cDb |
| Member name | Value | Description |
|---|---|---|
| Caching | 0 | The cDbClassInstance resides in the cache. This is the normal state for cached objects on the client side. |
| Initializing | 1 | The cDbClassInstance is being initialized. When a database driver starts to load an instance from database, it will always start in the in this state. After loading, the driver should call CommitChanges to switch to Caching state. |
| Initialized | 2 | Instance is intialized, but not yet in cache. |
| Creating | 3 | The cDbClassInstance is being created. Note that this state will never appear on the actual cached instance, but on a template instance that has been retrived via call to Add instead. Instances with this state will eventually end up Discarded. |
| Updating | 5 | The cDbClassInstance is in under update. Note that this state will never appear on the actual cached instance, but on the clone that has been retrived via call to BeginUpdate instead. Instances with this state will eventually end up Discarded. |
| CreatingExact | 7 | Internal, do not use |
| UpdatingExact | 9 | Internal, do not use |
| IdOnly | 10 | Internal, do not use |
| Null | 12 | Internal, do not use |
| Discarded | 16 | The cDbClassInstance has been discarded and is not in the cache. This state will appear after you have successfully completed updating of an instance. Discarded instances are no more connected to database in any way and refrences to them should be destroyed (to free up the memory). |
| Deserializing | 32 | The deserialization of cDbClassInstance is on the way. This state should appear only when using remoting. |
| Destroyed | 48 | The cDbClassInstance has been destroyed from database and cache. This state typically appears after the item has been deleted from database. Destroyed instances are no more connected to database in any way and refrences to them should be destroyed too (freeing up the memory). |