[EMAIL PROTECTED] wrote:
Additional information I can provide is:
...
I attempted to disable pysqlite2 (2.0.5) by renaming the pysqlite2 directory to
pysqlite2.old and then reinstalled a fresh version of pysqlite 1.1.6, still
using the sqlite3 converted database (it appeared to work) does this sound ok??
I did this as there are conflicting reports on the web about whether pysqlite2
actually works with trac correctly. Any comment on this?
pysqlite 2.0.5 was the right choice for Trac (provided you followed the
instructions in http://projects.edgewall.com/trac/wiki/PySqlite, that is,
that you have compiled sqlite-3.2.[78] in thread-safe mode).
I looked at the tables in sqlite3 converted database and the correct content
appears to be there so it really seems like there is something wrong with trac.
I don't think you have a problem with the db.
Are there any sensible tests I can perform to try and debug this further?
Yes, try to use tracd first
(http://projects.edgewall.com/trac/wiki/TracStandalone).
If it works in that setup, you know you have a problem with your apache
config.
-- Christian
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
