-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
> On Fri, Dec 29, 2006 at 02:18:08PM -0500, Benji York wrote:
>> Stefan H. Holek wrote:
>>> Do we have a history-less (i.e. no-grow) FileStorage?
>> There have been discussions and implementations of packless storages in
>> the pas
I'm sure you're probably aware of these, but I thought I'd file this
summary while they were in my head.
There is no history-less FileStorage. It is essentially a transaction log.
Directory Storage has Minimal.py which is history-less, very simple
though it is not proven in production. Could b
On Fri, Dec 29, 2006 at 02:18:08PM -0500, Benji York wrote:
> Stefan H. Holek wrote:
> >Do we have a history-less (i.e. no-grow) FileStorage?
>
> There have been discussions and implementations of packless storages in
> the past. As far as I know none have attained wide adoption.
> --
One of t
Stefan H. Holek wrote:
Do we have a history-less (i.e. no-grow) FileStorage?
There have been discussions and implementations of packless storages in
the past. As far as I know none have attained wide adoption.
--
Benji York
Senior Software Engineer
Zope Corporation
__
On Friday 29 December 2006 11:26, Tino Wildenhain wrote:
> Stefan H. Holek schrieb:
> > Do we have a history-less (i.e. no-grow) FileStorage?
>
> How do you think it should work? I mean, technically
> in theory? How would you implement MVCC?
Well, it is basically a "pack" after each write access.
Stefan H. Holek schrieb:
Do we have a history-less (i.e. no-grow) FileStorage?
How do you think it should work? I mean, technically
in theory? How would you implement MVCC?
Regards
Tino
___
For more information about ZODB, see the ZODB Wiki:
http://w
Do we have a history-less (i.e. no-grow) FileStorage?
Thanks,
Stefan
--
Anything that, in happening, causes something else to happen,
causes something else to happen. --Douglas Adams
___
For more information about ZODB, see the ZODB Wiki:
http://www
