Bug 31118 - Table PROPERTIES: property value for "version-set" gets too long
Summary: Table PROPERTIES: property value for "version-set" gets too long
Alias: None
Product: Slide
Classification: Unclassified
Component: Versioning (show other bugs)
Version: 2.1
Hardware: All All
: P3 normal (vote)
Target Milestone: ---
Assignee: Slide Developer List
: 31020 (view as bug list)
Depends on:
Blocks: 31521
  Show dependency tree
Reported: 2004-09-08 14:52 UTC by Roman
Modified: 2005-12-19 08:20 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Roman 2004-09-08 14:52:06 UTC
While using version-control on a file repeatedly after a while
"ORA-01401: inserted value too large for column" (e.g. with ORACLE store) occurs.
Affects: some of the stores -> table PROPERTIES, column PROPERTY_VALUE.
Identified limitation: 	"PROPERTY_VALUE" VARCHAR2(255), some stores use type "text" and avoid the limitation.

- use a store with mentioned limitation ("PROPERTY_VALUE" VARCHAR2(255)), in this case it was the oracle store)
- upload file
- put file under version control
- replace file 5 or few more times

The limit was reached after replacing a versioned file 5 times. The property name in this case was "version-set".

select max(length(property_value)) from properties t
--> 368
Ann: File was versioned 8 times. 

Possible workaround for ORACLE store (?): altering PROPERTY_VALUE to CLOB
Comment 1 Davide Savazzi 2004-09-08 15:24:30 UTC
*** Bug 31020 has been marked as a duplicate of this bug. ***
Comment 2 Davide Savazzi 2004-09-08 15:31:52 UTC
Quick fix for Oracle: change VARCHAR2(255) to VARCHAR2(4000)    
To Do:    
Comment 3 Rob Nielsen 2005-12-19 04:35:56 UTC
One possible solution (that we have implemented on our project) would be to
change the type of the PROPERTY_VALUE column from VARCHAR2(4000) to CLOB. While
varchars have a limitation of 4000 bytes clobs limitation is 4Gb, which should
be sufficient for most usages.
Comment 4 Ray Sprinkle 2005-12-19 17:20:35 UTC
For Oracle that is not the only size issue. Anywhere a parameter on a prepared 
statement is set the parameter length is limited to 4000 bytes.  I believe 
there is 1 place in the code where this occurs.  Also be aware that the 
property queries can only use non-indexed searches when examining property