There are many objects involved in saving data in an Enterprise Objects application. The objects you’ll most commonly work with are introduced here.
In Enterprise Objects, saves to the database most often originate with a saveChanges invocation on an editing context.
This object is responsible for figuring out which data source corresponds to the changes in a particular editing context. A given editing context can contain enterprise objects that are constituted from various data sources, so the object store coordinator manages the logistics of identifying these data sources when saving.
Each cooperating object store in an application is responsible for transmitting to its data source the changes handed to it by the object store coordinator. A cooperating object store (which is most often an instance of EODatabaseContext) is an abstract representation of a data source.
Other objects are involved in saving data, such as EODatabaseContext and EOAdaptorChannel, but you rarely need to interact with these objects programmatically.
Last updated: 2007-07-11