Object state changes

• Previous message: Andrus: "build.xml update"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

- When data object attribute value is modified, object's state changes:
COMMITTED -> MODIFIED
- When data object "to one" relationship is modified, object state
changes: COMMITTED -> MODIFIED

Question:
When data object "to many" relationship changes, on commit nothing would
change in the database for this object (since "to many" relationship is
FROM PRIMARY KEY). Any ideas for/against changing the object state to
MODIFIED in this case?

My argument AGAINST (this is the way I have it in Cayenne right now):
when building cascading update statements on commit in DataContext we
save some CPU cycles since we do not need to merge snapshots of objects
that will not result in SQL update anyways

Any comments?

-- 
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
- Andrei (a.k.a. Andrus) Adamchik
http://objectstyle.org
email: andrus at objectstyle dot org

• Next message: Andrei Adamchik: "Anonymous CVS access to cayenne is back"
• Previous message: Andrus: "build.xml update"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Mon Feb 04 2002 - 20:06:19 EST