Re: [SQLObject] Precedence of manually installed pysqlite

[Oleg B. <ph...@ph...>]

On Thu, Nov 27, 2008 at 11:07:31PM +0100, Markus Gritsch wrote:
> On Thu, Nov 27, 2008 at 10:09 PM, Dan Pascu <da...@ag...> wrote:
> > On Thursday 27 November 2008, Oleg Broytmann wrote:
> >> > Or maybe some parameter to the dburi (like backend) would be simpler
> >> > and cleaner.
> >>
> >>    Either sqlite2://, sqlite3:// - or sqlite://...?backend=sqlite2.
> >
> > My preference would be towards the last example using a backend parameter
> 
> Me too.  Using 'sqlite2' as name is IMO not correct.  'pysqlite2'
> would be more appropriate but this makes it look weird at the URI
> beginning.  Appending ?backend=sqlite3 or ?backend=pysqlite2 looks
> nice.

   I did the first step to implement this - removed global variables;
imported DB API driver stored as self.module. I hope to implement backend
selection next week.

> > Also the backend arg should be just a preference, which should override
> > the default choice of the most recent backend as is done now.
> 
> Currently the precedence is
> 1. sqlite3
> 2. pysqlite2
> 3. sqlite
> 
> Since sqlite3 is bundled with Python, it get's outdated by more recent
> versions of pysqlite2 quite quickly.  So if it is desired to have as
> default the most recent version, the default order if no parameter is
> specified should be
> 
> 1. pysqlite2
> 2. sqlite3
> 3. sqlite

   This was changed in 0.11.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.