Bron Gondwana wrote:
Don't worry, I've got some more patches for you!
cyrus-skiplist-transactions-2.3.10.diff
It's pretty well documented in the diff header. Basically, if a
transaction was open on a database and you made a read-only query
without a transaction on it (actually, any other query without
passing the _SAME_ transaction object) it would screw up royally.
Not to mention that passing a transaction at all after it had been
used in a commit or abort would have made a mess.
What patches do you run that uncovered these problems? Are these
skiplist-specific problems or are they present in any cyrusdb backend?
I'm trying to figure out if we're trying to do something with dbs that
the API wasn't designed to handle.
cyrus-skiplist-transactionuse-2.3.10.diff
Applied to CVS.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
