-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesus Cea wrote:
> In any case, thinking about that, any (reasonable) overhead is tolerable
> if you remember that you will be doing a syncronous disk write, finally.
> And you only can do about 60 per second with usual hardware.

Of course this is true if the transaction ends with any object
modification to be written in the commit(). If most transactions are
read only, you pay for nothing. So a configurable option would be
useful. Perhaps an explicit connection method a programmer could call
when doing the commit, or a commit parameter. Or a new *optional*
"begin_transaction()" that does an "abort()" to sync the cache, with an
optional parameter to move all cached object to the "untouched" state,
or "ghost" state+caching.


- --
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

iQCVAwUBREqfkJlgi5GaxT1NAQI2fAP/cUZ3oBJapLXPFSedoa3ckmbSThxJ4va1
98L07wAT6mjPH7Q2lzqeHC3jC1Ul8UVTtx+lwLJl7WqUyU3kG5HoFOWqjQP6nclF
zTiQpBTbM1uxIkmoS9SYT+vZJqIIxIjNbEuRKw7Qn+XNI0VCjOhR30iTDNjvaJq+
bao/IdcWxRM=
=4pum
-----END PGP SIGNATURE-----