[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635?page=c...
]
Strong Liu commented on HHH-4635:
---------------------------------
okay, again, anyone has a test case can reproduce this?
i use below test but it works fine
{code}
@Entity
public class Item {
@Id
@GeneratedValue
Long id;
@Lob
String longDescription;
@Column(length = 4000)
String shortDescription;
}
{code}
{code}
Session session = openSession( );
session.beginTransaction();
Item item = new Item();
char[] bytes = new char[4000];
for(int i= 0;i<bytes.length;i++){
bytes[i] = 'a';
}
item.longDescription=new String(bytes);
item.shortDescription=new String(bytes);
session.persist( item );
session.getTransaction().commit();
session.close();
{code}
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