[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2669) Unequivocally map MySQL LOB types to the LONG variant
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669?page=c...
]
Mark Matthews commented on HHH-2669:
------------------------------------
Just a quick comment validating Steve's approach, since we discussed this in IRC on
freenode and I asked around internally (and went through the source of the server), and
this is indeed the case. The different BLOB/TEXT types seem to be designed to prevent
storage over-allocation, since MySQL doesn't have CHECK CONSTRAINT.
Unequivocally map MySQL LOB types to the LONG variant
-----------------------------------------------------
Key: HHH-2669
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669
Project: Hibernate3
Issue Type: Improvement
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.3
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