[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] fatal: database schema has changed

From: Jeremy Cowgar
Subject: Re: [Monotone-devel] fatal: database schema has changed
Date: Mon, 14 Mar 2005 15:55:48 -0500


> Conclusion: monotone needs to always keep the database locked 
> explicitly, in 
> some way that persists even over transaction boundaries.
> Bad part: there is no such mechanism in sqlite, at least as far as I can see. 
> maybe we should whine at upstream/submit a patch/both until they add one?  we 
> could in theory create our own locking around the database, but that's a 
> tremendous pain, and sqlite already has all the right locking stuff, just not 
> exposed correctly for us to use.

Why not open the database only when needed from the serve command? You
could easily add a lock mechanism using a table/field to disallow any
writes from taking place. Just an idea, but maybe there is a better way
to serve and use a repo from the same computer.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]