[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c...
]
Jeff Schnitzer commented on HHH-1501:
-------------------------------------
I don't have any objection to the choice of efficient default types for unspecified
lengths. However, if I specify @Column(length=65536) on a String field, I expect that
Hibernate's Derby dialect should be smart enough to make it a CLOB (or whatever type
can actually hold a 64k string).
Caveat: It was 3.5 years ago that I last considered this issue and I have no idea what
Hibernate will do with Derby today. If putting @Column(length=XXXX) on byte[] and String
types works properly, you should just close this issue.
insert long string (more than 32700) fails on derby
---------------------------------------------------
Key: HHH-1501
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.0-Beta-2
Environment: Derby 10
Reporter: Sergey Vladimirov
Priority: Trivial
http://issues.apache.org/jira/browse/DERBY-102
VARCHAR maximum length 32 672
LONG VARCHAR maximum length 32 700
CLOB maximum length 2 147 483 647
BLOB maximum length 2 147 483 647
this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with
change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira