automatic dirty check does not work with lobs --------------------------------------------- Key: HHH-4043 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4043 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.3.2, 3.3.1 Reporter: Stefan Wachter When a lob (a blob or a clob) is modified by truncate or by setOutputStream/setCharacterStream then field is not detected as being dirty. The reason seems to be that the BlobType and ClobType determine the dirtyness of such fields by checking object identity of the java.sql.Blob / Clob members. Maybe the behaviour could be improved by the following way: - Blobs and Clobs seem always to be wrapped by org.hibernate.lob.SerializableBlob / SerializableClob - These classes could be augmented by a dirty flag that is set if truncate or setOutputStream / setCharacterStream is set - The BlobType/ClobType should no more determine the dirtyness by checking object identity but by using this flag -- 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