Next: Limits, Previous: Administration, Up: Overview [Contents][Index]
Library functions may fail for whatever reason (memory allocation, I/O operations, etc). When they do the in-memory database may get in an unintended state, or worse, in an unusable state. When they do there’s very little left to do beyond closing the database. Reopening after closing would work fine, though the changes made after the last completed transaction would be lost.
The on disk database will stay in an intended state at all times, with recorded data reflecting the last successful transaction (bar hardware and operation system failures and bugs in the nonblonde library).
See Data Integrity.
There is currently no support for rolling back transactions for this library version. The condition may be helped by closing and reopening the database.