Up DevForce development


Last modified on August 15, 2012 17:21

If an application decides to save, it issues one of the overloads of EntityManager.SaveChanges that can save an individual business object, an arbitrary list of objects, or all entities with pending changes.

Saves are always transactional in DevForce.
Unmodified entities are never saved. Attempts to save them are ignored.

If concurrency checking is enabled, DevForce will confirm that entities being saved have not been modified or deleted by another process since they were last retrieved.

The application can determine if a particular object is new, modified, marked for deletion, or unmodified by examining its EntityState property which returns one of the corresponding EntityState enumerations.

Initiation of any save operation causes the EntityManager to attempt to replace temporary ids with permanent ids. 

Add, change, and delete operations only affect entities in an EntityManager's entity cache. They are not written to the data source nor are they visible to other application users until the application tells the EntityManager to save them. Alternatively, the application can undo the changes rather than save them.

Save-related topics elaborate on these points.

Created by DevForce on February 08, 2011 12:08

This wiki is licensed under a Creative Commons 2.0 license. XWiki Enterprise 3.2 - Documentation. Copyright © 2015 IdeaBlade