[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c...
]
Steve Ebersole commented on HHH-1501:
-------------------------------------
{quote}
I should be able to declare a byte[] field in Java and Hibernate should figure out how to
map that to various databases.
{quote}
Its not a question of "various databases". Its a question of "various JDBC
types". And that part we have done. That is why there is a StringType
(String->VARCHAR), a MaterializedClobType (String->CLOB), etc. All you have told
Hibernate is "I have a String". Again, short of querying the JDBC metadata for
that column (which will not happen, see previous comment) how are you thinking HIbernate
is supposed to know that this particular String property is a CLOB while some other
property is a VARCHAR?
Why is it soooooo unreasonable that you tell it "hey, use your super-duper
'materialized_clob' type for this particular property"?
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