durusmail: durus-users: BerkeleyDB Backend Storage Engine for DURUS release 20061005
BerkeleyDB Backend Storage Engine for DURUS release 20061005
2006-10-05
BerkeleyDB Backend Storage Engine for DURUS release 20061005
Jesus Cea
2006-10-05
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

BerkeleyDB Backend Storage Engine for DURUS
http://www.argo.es/~jcea/programacion/durus-berkeleydbstorage.htm

Know How Durus 3.4 (not yet updated to Durus 3.5)
http://www.argo.es/~jcea/artic/know_how-durus-3_4.htm

"""
NOTE: Although documentation is not yet updated, this release works just
fine under Durus 3.5 release.

* Upgrade Instructions:

o "do_recover" constructor parameter default value changed from "False"
to "True". Better play safe than sorry. Of course you can do
"do_recover=False" if you know what are you doing.

If you are opening the storage "read_only", you must set this flag to False.

o This release adds an optional "async_log_write" parameter to storage
instance constructor. This option is only relevant when you use "non
durable" storages. You can now choose between "in memory" and "async
write" transaction logging.

If you are using "non durable" storages, and you want to keep the
previous behaviour, you MUST use "async_log_write=False". The new
default will use asynchronous writes for the transactional logging.

* Changes:

o 20061005 - r217 - jcea@argo.es

"do_recover" constructor parameter default value changed from "False" to
"True".

o 20061003 - r215 - jcea@argo.es

"KNOW_HOW-DURUS" updated to document a sort of persistent weak reference
pattern.

o 20061003 - r214 - jcea@argo.es

"KNOW_HOW-DURUS" updated to document BTree abilities.

o 20060927 - r205 - jcea@argo.es

New "in use" flag inside the database storage. If a storage is opened
and that flag is set, a database recovery is done.

That flag is cleared when the storage instance destructor is called.

This flag is not used if the database is opened in read only mode.

o 20060927 - r202 - jcea@argo.es

When the storage is opened read/write and non durable, the storage
instance destructor will try to (synchronously) flush the transaction log.

This last flush can't be garanteed, nevertheless.

o 20060927 - r200 - jcea@argo.es

Add a new optional parameter to the constructor: "async_log_write".
"""

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRSU3Y5lgi5GaxT1NAQJdgwP+PTzst8Nbjr+qoOcZ3Ys2W2+ZfEgCtHE/
18o6ZzVwtTi75aS5GU0ku4oCmbR/U3meZ8q4emWw2+wD/AvskhHuU5Cb++VPmDN4
70qWRfmUlQHx/6NBlReVULjs2zFaWP9JaaNgph3ijsY9ua1LHy1dOu1r8njv70HY
AH76AfOwTkk=
=JTNH
-----END PGP SIGNATURE-----
reply