hamsterdb 1.0.4 - Release Notes

This release implements the first of several steps towards ACID transactions.
Currently, the following limitations apply:

There can only be one Transaction at a time. If one Transaction was created, and ham_txn_begin is called a second time, the function will fail with HAM_LIMITS_REACHED
Since the function ham_env_erase_db internally creates a Transaction, the previous rule also applies here and ham_env_erase_db can also fail with HAM_LIMITS_REACHED
Currently, when a Transaction is aborted, the log file is used to undo all changes. Therefore logging is automatically enabled when transactions are used (in other words: HAM_ENABLE_TRANSACTIONS currently implies HAM_ENABLE_RECOVERY).
When closing the Database or Environment (with ham_close or ham_env_close), and a Transaction is still open, then this Transaction will automatically be aborted.
The C++ wrapper does not yet implement the Transaction class.
The Transaction API (ham_txn_*) is not stable and subject to change.
New Features
- Transactional support can be enabled with the flag HAM_ENABLE_TRANSACTIONS
Bugfixes
- When creating several Databases in an Environment, and recovery was enabled, each Database created its own log object and the log was corrupted
- Minor grammar changes in the documentation (header file comments)
- Unittests no longer fail if the library was compiled without support for compression, encryption or internal functions
Other Changes
- none
Known Issues
- none
For more information, read the README and the CHANGELOG.