On 9/23/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote: > > You're going to have a problem with the transaction handling here -- > > the server does not and can not wrap a client connection into a single > > transaction. The problem is that the server is multiplexing across > > multiple connections at once, but with sqlite (and RDBMSes generally, > > to some extent) there is no way to have multiple parallel transactions > > open at the same time, to keep separate the data that's arriving in > > parallel from multiple clients. So the server commits regularly. > > Hmmm... interesting point. Thanks for the hint. You're right, the > concurrent incoming connections could make real trouble here. I've to > investigate to see whether a workaround is possible or whether we really > hit against the wall here. Many thanks for clarifying this point.
I've thought for a while that we should have a "local_undo" command that reverted the most recent change to the local database, whatever it was. Perhaps your situation could benefit from the same infrastructure that that would need. http://www.sqlite.org/cvstrac/wiki?p=UndoRedo might be a good starting point. zw _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
