[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635?page=c...
]
Jonathan Tougas updated HHH-4635:
---------------------------------
Attachment: oracleLobTest2.zip
Attaching a test case which should allow you to reproduce the issue. I figured out that
the key ingredient is to have a database configured with a multi byte character set. Let
me know if you need anything else.
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
Attachments: oracleLobTest2.zip
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