Jesus Cea  wrote:
> Current durus has objects in one of three status:
>
> SAVED: Object is in cache, unmodified
> UNSAVED: Object is in cache, modified
> GHOST: Object is not yet loaded.

My "seen" set would include all objects that have been in the SAVED
state at some point during the transaction.

> The problem with current approach is "false conflict". The cost of
> redoing an entire transaction, unnecessary, to cope with false conflicts
> seems pretty high. If the cost of intercepting first attribute access
> (only the first one!) is low (should be), then we should do it.

That depends on the nature of the application.  For the applications
I deal with it would be almost a pure loss (conflicts are rare).

> Anything more that I can do to convince you?

A patch?  If it can be done cleanly and is not too expensive then I
think it would be accepted.

  Neil