|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
After discussing this further, we think it's best to reject – I reverted the changes.
VARBINARY is intended to use "varchar
for bit data" only. If a byte[] field needs more than the 32k size limit, please use:
@Lob (for annotated entities)
or
type="materialized_blob" (for HBM mapped entities)
If we allow a Hibernate VARBINARY to map to an SQL blob, JDBC's getBytes will be used to translate back to VARBINARY. For SQL blob types, that doesn't always work. DB2/Derby's JDBC drivers appear to support it, but others do not. For consistency, we'd rather leave it as is.