Re: [Monotone-devel] mtn: error: sqlite error: database is locked

[Chad Walstrom]

Alvaro Herrera <address@hidden> wrote:
> fulfills higher-level integrity constraints.  In Monotone's case, my
> guess is that the ancestor tree needs several additional checks, but
> they are probably implementable by using triggers or other
> mechanisms).

How deep does the rabbit hole go?  Now we're getting into questions
about whether or not the database should do work other than storing and
retrieving data.  Personally, I'm not a fan of programming in-database,
but there are times when it makes sense to do so.  Obviously, the
database cannot understand those higher-order objects, it's up to
Monotone to draw meaning from them.  Likewise, it's up to Monotone to
decide what is a safe transaction and an unsafe transaction relative to
those objects.  It's up to the database to make sure that the decisions
Monotone makes become permanent, safely.  As it was stated earlier in
this thread, making montone friendly to different types of transactions
is going to take some API changes.