[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669?page=c...
]
Max Bowsher commented on HHH-2669:
----------------------------------
I just upgraded from 3.2.x to 3.3.x (yes, a bit late, I know) and found my generated
schema changing types under me. OK, that I more-or-less expected.
But I did expect that I ought to be able to override Hibernate's default decisions
using <property length="NNNN"/>.
I've got no problem with changing the default to be the long* variants, but surely an
explicit length request should still select the most appropriate MySQL type?
Unequivocally map MySQL LOB types to the LONG variant
-----------------------------------------------------
Key: HHH-2669
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669
Project: Hibernate Core
Issue Type: Improvement
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.3.0.CR1
MySQL differentiates different "sizes" of LOBs. Apparently, the smaller types
offer no storage benefit nor performance gain. So we should consider mapping the LOB
types in the MySQL dialect to the LON variants in all cases.
The current setup causes truncation headaches for users, apparently unnecessarily.
--
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