On Thu, Nov 27, 2008 at 09:01:41PM +0200, Dan Pascu wrote:
> I think that such a change should not be applied at all. This change will
> make some users happy, but will alienate others, who what to use the old
> default while they may have both installed for reasons of their own.
> There shouldn't be a hardcoded choice of one version over the other if
> everybody is to be happy (the assumption that all people having both
> sqlite3 from python2.5+ and pysqlite2 installed prefer pysqlite2 doesn't
> hold water; same for the other way around)
Yes, you have a point.
> A better solution would be to somehow (maybe using a module parameter)
> indicate which is preferred (having a default that points to the most
> common/used one in case nothing is indicated by the user).
>
> Or maybe some parameter to the dburi (like backend) would be simpler and
> cleaner.
Either sqlite2://, sqlite3:// - or sqlite://...?backend=sqlite2.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
