[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c...
]
Jeff Schnitzer commented on HHH-1501:
-------------------------------------
I'm in agreement with Sergey.
I have developed some software that *theoretically* can be deployed on any database. This
is one of the promises of ORM, no? In practice, this doesn't really work very well,
and this is one of the reasons why.
I should be able to declare a byte[] field in Java and Hibernate should figure out how to
map that to various databases. You can point at Derby as broken (maybe it is) but the
bottom line is that this is something the ORM layer should worry about, not individual
developers - or worse - the poor bastards that download my code and try to run it against
their obscure XYZ database. I'd like to say that my software works "on any
database with a Hibernate dialect" but instead I have to say that my software works
"on any database with a *working* Hibernate dialect".
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