5:39 a.m.
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
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:16 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
K C commented on HHH-5811:
--------------------------
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
The database properties can be configured in unitils.properties and the current maven
dependency for the Oracle jdbc must be set in pom.xml.
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
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
K C edited comment on HHH-5811 at 1/3/11 4:56 AM:
--------------------------------------------------
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
For the sample, the db is an in memory HsqlDb (normally we run on Oracle)
was (Author: kccoyote):
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
For the sample, the db is an in memory HsqlDb (normally we run on Oracle)
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
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
K C edited comment on HHH-5811 at 1/3/11 4:56 AM:
--------------------------------------------------
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
For the sample, the db is an in memory HsqlDb (normally we run on Oracle)
was (Author: kccoyote):
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
The database properties can be configured in unitils.properties and the current maven
dependency for the Oracle jdbc must be set in pom.xml.
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
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:59 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
K C updated HHH-5811:
---------------------
Attachment: hhh-5811.zip
added test case
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:01 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
K C edited comment on HHH-5811 at 1/3/11 4:59 AM:
--------------------------------------------------
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
For the sample, the db is an in memory HsqlDb (normally we run on Oracle)
was (Author: kccoyote):
Added sample.
When executing 'mvn test', 3 out of the 4 tests should succeed, one fails. The
only differenece being the type of the field: Byte[] fails, byte[], Character[] and char[]
work.
With Byte[], Hibernate issues an additional update, as can be seen in stdout:
Hibernate: select testentity0_.id as id0_0_, testentity0_.nativeByteArray as
nativeBy2_0_0_, testentity0_.nativeByteWrapperArray as nativeBy3_0_0_,
testentity0_.nativeCharArray as nativeCh4_0_0_, testentity0_.nativeCharWrapperArray as
nativeCh5_0_0_, testentity0_.version as version0_0_ from TestEntity testentity0_ where
testentity0_.id=?
Hibernate: update TestEntity set nativeByteArray=?, nativeByteWrapperArray=?,
nativeCharArray=?, nativeCharWrapperArray=?, version=? where id=? and version=?
For the sample, the db is an in memory HsqlDb (normally we run on Oracle)
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner updated HHH-5811:
-----------------------------
Fix Version/s: 4.0.0.Alpha1
3.6.1
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
Fix For: 3.6.1, 4.0.0.Alpha1
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:19 a.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner reassigned HHH-5811:
--------------------------------
Assignee: Gail Badner
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
Assignee: Gail Badner
Fix For: 3.6.1, 4.0.0.Alpha1
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:53 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner updated HHH-5811:
-----------------------------
Fix Version/s: (was: 3.6.1)
3.6.2
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
Assignee: Gail Badner
Fix For: 3.6.2, 4.0.0.Alpha1
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner updated HHH-5811:
-----------------------------
Fix Version/s: (was: 3.6.2)
(was: 4.0.0.Alpha1)
4.0.0.Alpha3
3.6.3
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
Assignee: Gail Badner
Fix For: 3.6.3, 4.0.0.Alpha3
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:57 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Steve Ebersole updated HHH-5811:
--------------------------------
Fix Version/s: (was: 3.6.3)
3.6.4
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
Assignee: Gail Badner
Fix For: 3.6.4, 4.0.0.Alpha3
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner updated HHH-5811:
-----------------------------
Fix Version/s: (was: 3.6.4)
(was: 4.0.0.Alpha3)
4.0.0.Beta1
3.6.5
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
Assignee: Gail Badner
Fix For: 3.6.5, 4.0.0.Beta1
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5811) flush causes update query on field of type Byte[]
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811?page=c...
]
Gail Badner updated HHH-5811:
-----------------------------
Assignee: (was: Gail Badner)
Fix Version/s: (was: 3.6.5)
(was: 4.0.0.Beta1)
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4970
days inactive
5136
days old
hibernate-issues@lists.jboss.org
13 comments
3 participants
participants (3)
-
Gail Badner (JIRA) -
K C (JIRA)
-
Steve Ebersole (JIRA)