[kepler-dev] [Bug 5302] module_dependencies column defined too short
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Thu May 5 12:49:15 PDT 2011
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5302
--- Comment #3 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-05-05 12:49:15 PDT ---
I've found another 255-char limit truncation issue, but this issue *does*
affect our default hsql provenance dbs: parameter's value column gets chopped
off at 255. This is far too small for e.g. a String Constant with value set to
a large block of text. Apparently hsql is enforcing varchar length for this
column -- the only difference I notice between it and a varchar(255) column
with length not being enforced is that it has Nullable set to true instead of
false.
For reference I did find text confirming hsql doesn't necessarily enforce
column size:
-------
HSQLDB databases are initially created in a legacy mode that does not enforce
column size and precision. You can set the property:
sql.enforce_strict_size=true to enable this feature. When this property has
been set, Any supplied column size and precision for numeric and character
types (CHARACTER and VARCHAR) are enforced. Use the command, SET PROPERTY
"sql.enforce_strict_size" TRUE once before defining the tables.
http://www.hsqldb.org/doc/guide/ch09.html#create_table-section
-------
--
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Kepler-dev
mailing list