[Trac] Re: Trac and sqlite3

[Christopher Lenz]

Clay Loveless wrote:
> On 3/7/05 9:16 AM Pacific Time, Christopher Lenz (cmlenz at gmx.de) wrote:
> 
>>Actually, I think it's just a matter of choosing between pysqlite <= 1.0.x
>>and pysqlite >= 1.1.x. The latter uses the SQLite 3 APIs, while the former
>>uses SQLite 2.
>>
>>This has the side-effect that you can't have both SQLite 2 and 3 Trac
>>environments on the same machine (without some hacking), because the
>>choice is made by which pysqlite version Trac finds on the Python path.
> 
> Hmmmm... This exceeds my current understanding of Python. : )
> 
> I recognize that my Python path is: /usr/lib/python2.3/site-packages
> (right?)

Looks right, yes.

> And I can see that `dpkg --list` tells me I've got python-sqlite 1.0.1
> installed.
> 
> I can also see that pysqlite.sourceforge.net points me to pysqlite.org,
> which has a lovely series of photos of some cats, but no helpful information
> about pysqlite 1.0 vs 1.1.
> 
> PyPI on python.org makes no mention of pysqlite beyond 1.0.

It's simple, really:
 * If you use PySQLite 1.0.x, Trac will use the SQLite 2.x APIs and
   you'll only be able to access SQLite databases created with SQLite
   2.x.
 * If you use PySQLite 1.1.x, Trac will use the SQLite 3.x APIs and
   you'll only be able to access SQLite 3.x databases.

Both are downloadable from the SourceForge project page:

  <http://sourceforge.net/projects/pysqlite/>

I have no idea what's wrong with pysqlite.org. Something weird going on :-P

> Not sure where to go from here. I'm not concerned about conflicting versions
> of sqlite ... Currently, all I'm using sqlite for is trac. I'm also not
> worried about compiling my own libraries, if necessary. Debian package
> installations are more convenient, but I don't mind getting out of those
> occasionally if there's a benefit.
> 
> Which brings me back to the sqlite2 vs sqlite3 performance question as it
> relates to trac. Based on the "Improved Concurrency" section of this
> document:
> 
> http://www.sqlite.org/version3.html
> 
> ... I'm assuming that's a benefit to a busy trac project in terms of
> performance. Chris, can you please address that question?

While I also *think* that SQLite 3 should give better performance (from
reading that document), I really can't say anything more. I've done no
load-testing or anything of SQLite 2 vs. 3 myself. Maybe someone else has?

Cheers,
Chris
-- 
Christopher Lenz
  cmlenz at gmx.de
  http://www.cmlenz.net/