On Sat, 12 Oct 2002, Ilya Martynov wrote:
> >>>>> On Fri, 11 Oct 2002 17:19:51 -0500 (CDT), Dave Rolsky <autarch@...> said:
> DR> The whole caching system is actually do for an overhaul sometime
> DR> soon anyway, but I'll try to fix this first, get a release out,
> DR> and then start breaking it again.
> Does this overhaul means that Alzabo will finally support transactions
> correctly when caching is turned on? Can you give some details on the
> new caching architecture? I just want to check that it is compatible
> with all transactions-with-caching scenarious I know about.
I have two big goals for overhauling caching:
1. Store a bit more info in the cache so I can finally support "batch"
update & delete operations, with something like:
$Table->update( set => ..., where => .... );
The main reason I didn't do this long ago was that the cache does not know
what table a cached object belongs to.
2. Make sure clearing the cache _works_ and makes sense. Right now
the clear method really only affects the process that calls it, not the
whole cache. There probably needs to be semantics for clearing locally
3. Add transaction support inasmuch as possible. For example, if you used
the ::RDBMS sync & store modules together, and it pointed to the same
schema as the one you're using for data, it'd be trivial to add
For the BerkeleyDB sync or store modules, we can use BerkeleyDB's
transaction support. For the other modules, I'm not sure how to approach
it, or if it's even worth doing anything besides simply calling clear on
The problem is just finding the tuits to do all this.
we await the New Sun