OJB
Downloads
Documentation
Development
Translated (Web)
|
Notes on Using the ODMG API |
Transactions |
The ODMG API uses object-level transactions, compared to the PersistenceBroker
database-level transactions. An ODMG Transaction instance contains
all of the changes made to the object model within the context of that
transaction, and will not commit them to the database until the ODMG
Transaction is committed. At that point it will use a database
transaction to ensure atomicity of its changes.
|
Locks |
The ODMG specification includes several levels of locks and isolation. These are
explained in much more detail in the Lock Manager
documentation.
In the ODMG API, locks obtained on objects are locked within the context
of a thread. Any object modified within the context of a transaction will
be stored with the transaction, however changes made to the same object
by other threads will also be stored. The ODMG locking conventions ensure
that an object can only be modified within the transaction on the locking thread.
|
|
|