Summary
Configures db4o to generate commit timestamps for all stored objects.
All the objects commited within a transaction will share the same commit timestamp.
All the objects commited within a transaction will share the same commit timestamp.
- Assembly
- Db4objects
.Db4o-2010 .dll - Namespace
- Db4objects
.Db4o .Config - Containing Type
- IFileConfiguration
Syntax
bool GenerateCommitTimestamps { set; }Remarks
Configures db4o to generate commit timestamps for all stored objects.
All the objects commited within a transaction will share the same commit timestamp.
This setting should be used when the database is first created.
Afterwards you can access the object's commit timestamp like this:
All the objects commited within a transaction will share the same commit timestamp.
This setting should be used when the database is first created.
Afterwards you can access the object's commit timestamp like this:
ObjectContainer container = ...;
ObjectInfo objectInfo = container.ext().getObjectInfo(obj);
long commitTimestamp = objectInfo.getVersion();
Value
| Type | Description |
|---|---|
| bool | if true, commit timetamps will be generated for all stored objects. If you already have commit timestamps for stored objects and later set this flag to false, although you wont be able to access them, the commit timestamps will still be taking space in your file container. The only way to free that space is defragmenting the container. |