Please note: this project is inactive since early 2006

5.1 Bringing transactions to the object world

A nested EditingContext is the solution for the problem. It provides a clean and convenient way of making changes on an other EditingContext, while exposing three of the four ACID properties at the object level:

In other words, you can think of a nested EditingContext as a transaction made at the object level.

Moreover, any object you will get in a nested EditingContextwill reflect the changes made on it in its parent, even the uncommitted/unsaved ones, e.g. inserted objects will show up in the result set of a fetch, but deleted objects won't.

Comments are welcome: Sebastien Bigaret / Modeling Home Page
Hosted Logo