I would like to use cascading update, but am concerned about the overhead involved in updating objects in the graph that have not changed.
Would this modification make sense, or is it naive? 1. Create a new interface called IDirtyAware or something similar that contains an "isDirty()" method. Any object can optionally implement this interface. 2. In the "executeUpdate()" method of whoever implements the JdbcAccess interface (currently JdbcAccessImpl), a check is done against the object: a. if it doesn't implement IDirtyAware, processing continues as it does today. b. if it does implement IDirtyAware: 1. If dirty, processing continues as it does today. 2. If not dirty, no update is performed, but the object graph continues to be traversed. Possible? I imagine I'm missing something major, but I'd love to have something similar implemented. Gary __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
