A successful transaction commit results in a new consistent version. If explicitly named, this version becomes a historical database version, which can be accessed by its logical name in the future . Access is read-only, and does not require any locking mechanism. Any application can request the latest available consistent database version, using a reference to current time, with no locking overhead. Support for High Level Consistency.
Developers can describe very complex consistency methods and rules using daemons and triggers.
These methods can be attached to particular events such as, before or after creation, as well as class, instance, attribute modification. Daemons and triggers provide for message propagation within your database. This results in a very intelligent database, which can be event driven.