1) This doesn't require any action to unlock, the lock is only present will a writer transaction is open.
2) These get less frequent with each new version of SQLite. If you handle less than ~10 requests per second, I've found it hard to run in to this. --Noah On Sep 21, 2007, at 10:45 AM, Alexander Neundorf wrote: > > On Thursday 20 September 2007 03:29, Christian Boos wrote: >> Jeff Webb wrote: >>> what are the "limitations of mysql" that you refer to? >>> >>> if mysql is not the preferred supported server then is SqlLite the >>> preferred backend? to that end how well does it scale? >> >> SQLite works quite well and if scaling is an issue, the solution >> is to >> migrate to PostgreSQL. >> The limitations and issues of MySQL that concern us are described >> here: >> >> http://trac.edgewall.org/wiki/MySqlDb > > With previous Trac versions we had quite often the ugly "Database > locked" > error and if I understood this correctly, the reason was that > sqlite is not a > db server but "just" an in-process db. The problem was basically > impossible > to reproduce, it just happened from time to time. > We ended up writing a hackish shell script which tries to detect > every minute > if Trac is locked (using ps, strace and other nice things) and if > so restart > the apache. This way the only workaround we found. > > So I actually hoped that Trac would support MySQL in the future > (this is > already installed on most systems, whereas PostgreSQL is not that > often > found). > > Bye > Alex > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
