Hey Shane,
Well, first feasibility. But I think it's doable. The question is how
much cruft it will require.
(I think on the high level a KVDB is a perfect match for a ZODB
backend. oid -> pickle is the mapping. If it's oid_tid -> pickle it's
still not bad.)
So if the story about a KVDB being supe
Adam GROSZER wrote:
> This is some tinkering about whether/how it is possible to make a ZODB
> storage that uses a simple kev-value database (KVDB) (e.g. tokyo tyrant).
> A KVDB that is persistent on disk or even replicated should not be
> less fault tolerant as MySQL.
I don't quite understand. W
Hello Shane,
This is some tinkering about whether/how it is possible to make a ZODB
storage that uses a simple kev-value database (KVDB) (e.g. tokyo tyrant).
A KVDB that is persistent on disk or even replicated should not be
less fault tolerant as MySQL.
As I see you got the caching right with me