[Hibernate] overhead of dirty tracking

[hanasaki]

How is the dirty flag maintained in hibernate to keep overhead low.  For 
example: I have many POJO that are mapped to table schemata.  Some 
reference others.  Some are aggregates of other, non-hibernate, object. 
 These may be aggregates of other objects etc in a complex hierarchy.

Any instance is implicitly dirty if any aggregate or aggregates 
aggregate, down the hierarchy, is dirty.  This seems like complex long 
tree traversals.  How can this overhead be minimized?

thanks
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel