[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635?page=c...
]
Jonathan Tougas commented on HHH-4635:
--------------------------------------
Until a test case is submitted (I'm working on one, but I have little time) if you
want to try to reproduce the problem the idea is to have hibernate create a insert
statement where there is a lob column _followed_ by 4000 bytes of data. So for the entity
above, if the insert statement is "insert into item (id, shortDescription,
longDescription) values(?,?,?)", then no the problem will not occur. However
depending on the order hibernate chooses, you can end up with an insert statement like
"insert into item (longDescription,id, shortDescription) values(?,?,?)", and if
the shortDescription parameter has 4000 characters, you should get the error.
Oracle ORA-24816 inserting and updating data for entities containg
LOB attributes
---------------------------------------------------------------------------------
Key: HHH-4635
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.1
Reporter: Clay Atkins
Assignee: Strong Liu
Priority: Critical
Inserting or updating an entity with LOB results in the following error from oracle:
{noformat}
Caused by: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after
actual LONG or LOB column
{noformat}
Fairly confident that the ordering of the LOB attributes is not putting them at the end
of the insert or the update. Oracle requires all LOB columns to be the last in the
statement.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira