Christopher Lenz wrote:
Hi folks,
I've just upgraded projects.edgewall.com to Trac 0.10dev (r2300).
I got a ''Database is locked'' error just now on p.e.c.
While I think it was not a bug per se, I have two remarks:
First, I noticed that it took some time (a few seconds) to detect
the lock, which makes me think we're still using pysqlite 2.0.x.
If so, we should consider upgrading to 2.1.3 or 2.2.0, where the
performance is better and the lock detection is quicker.
Then, the lock situation, if it still happens should (now?) be a
"normal" situation, indicating that two users tried to write to
the database at the same time: this shouldn't produce a "Oops".
One possible fix would be to produce an error page, with a
"Resubmit" button so that the user can try to post her query
again.
Another option would be to find a way to retry the query
automatically once or twice, without requiring another
round-trip to the user (if this fails again after the second
or third try, we can at that time revert to sending a TracError).
Thoughts?
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
