]
Gail Badner commented on HHH-5811:
----------------------------------
I've added code to test versioned entities with LOBs to master and 3.6.
This issue is reproduced by a "FailureExpected" test:
org.hibernate.test.annotations.lob.VersionedLobTest.testVersionUnchangedByteArray()
flush causes update query on field of type Byte[]
-------------------------------------------------
Key: HHH-5811
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.6.0
Environment: Hibernate 3.6.0.Final, Oracle 11g
Reporter: K C
Attachments: hhh-5811.zip
I have a field that is mapped as follows:
@Lob
@Column(name = "picture")
private Byte[] picture;
When retrieving the entity with a regular session.load() or criteria.list(), upon session
flush, an update statement is issued for the field.
In an interceptor, I can see in the onFlushDirty method that the byte arrays in the
currentState en previousState parameters are different objects, but with the same
byte-content. All the other objects in currentState and previousState are identical.
My guess is that this causes Hibernate to think the contents of the field changed?
This behavior did not happen in 3.5.5-Final, and because the entity is versioned, upon
each retrieval, the version field is incremented, which is highly undesirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: