When transactions are disabled, the current CVS build
of jdbm holds on to dirty page data indefinitely unless
the user explicitly calls commit().
This patch adds functionality to auto-commit whenever
the dirty page pool hits a certain, configurable limit.
The jdbm.disableTransactions.autoCommitInterval
property can be used to control the maximum size of the
dirty page pool.
This patch also causes RecordFile.rollback() to throw
an exception if transactions are disabled.
Logged In: YES
user_id=560111
Wooops - found a problem with the patch (sorry). Please use
the attached instead.
- K
Patch file with bug fix