Rene Rivera wrote:
On 11/28/2010 7:45 AM, Jim Bell wrote:
On 1:59 PM, Dean Michael Berris wrote:
On Sat, Nov 27, 2010 at 6:25 AM, Rene Rivera<grafikrobot@gmail.com> wrote:
On 11/26/2010 4:09 PM, Klaim wrote:
not sure if it's a revelant information but I tried the firs link and got a server error with this reason : "OperationalError: database is locked"
Yes - this is a well known issue with SQLite and Trac - the recommended solution is to migrate to Postgresql.
I just retried and it work correctly now.
Yes, I'm aware of, and trying to fix, that problem. It's intermittent, but recurring with sufficient propensity to be really annoying :-(
This is inherent in SQLite because it's designed to be a single-threaded embedded database. If there's an option to use BDB, PostgreSQL, or MySQL as the backing store, we can avoid this database locking issue.
The idea of switching to MySQL is something I've been investigating this past week (when I've gotten a chance from work) and it's not something that can be done easily, AFAICT. It essentially boils down to exporting, editing SQL, importing, and crossing fingers that Trac understands the new data.
Migrating to Postgresql works well and tools like PgAdminIII make additional administration trivial should you need it. The information here will help http://www.agile-trac.org/wiki/Documentation/MigratingToPostgresql. If you are having trouble PM me. Jamie