You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by bu...@apache.org on 2004/09/08 16:52:07 UTC
DO NOT REPLY [Bug 31118] New: -
Table PROPERTIES: property value for "version-set" gets too long
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31118>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31118
Table PROPERTIES: property value for "version-set" gets too long
Summary: Table PROPERTIES: property value for "version-set" gets
too long
Product: Slide
Version: 2.1
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Versioning
AssignedTo: slide-dev@jakarta.apache.org
ReportedBy: r.novak@iqsoft.at
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.
Reproduction:
- 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".
SQL-Query:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org