except i want hibernate to update these columns. the trick is to have hibernate send and receive the target columns to/from the database when doing an UPDATE, but when it is asked to merge the pojo, ignore them for deciding if the updated object is "dirty".
for the near term, i'm doing a brute force through the other attributes in a helper class "isDirty" method, but this ends up turning an O(n) test into O(2n) since hibernate is ALSO going to do this when it needs to decide if the underlying object is dirty before it commits the transaction. the issue isnt "updatability" but "significance". in my case, the editor and updated are necessary to tag an update but are not considered "significant" with regard to object "dirtiness". /sigh == stanton View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183357#4183357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183357 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
