On Thu, Nov 27, 2008 at 11:07:31PM +0100, Markus Gritsch wrote:
> On Thu, Nov 27, 2008 at 10:09 PM, Dan Pascu 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:/
On Thu, Nov 27, 2008 at 05:38:59PM +0100, Markus Gritsch wrote:
> On Thu, Nov 27, 2008 at 4:44 PM, Oleg Broytmann wrote:
> >
> > I think, though, that such a change should be applied to the trunk, not
> > to the bugfix-only branches.
>
> OK, I don't mind since I use a patched version in the mea
On Thu, Nov 27, 2008 at 11:07:31PM +0100, Markus Gritsch wrote:
> 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
On Thu, Nov 27, 2008 at 10:09 PM, Dan Pascu <[EMAIL PROTECTED]> 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 p
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,
because
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
On Thursday 27 November 2008, Oleg Broytmann wrote:
> On Thu, Nov 27, 2008 at 04:35:43PM +0100, Markus Gritsch wrote:
> > currently the sqlite3 module is, if present, preferred over a
> > manually installed pysqlite2 module. Therefore it is not possible to
> > use a newer version of pysqlite than
On Thu, Nov 27, 2008 at 05:38:59PM +0100, Markus Gritsch wrote:
> However, I wonder about the code in the isSupported() function in
> sqlobject/sqlite/__init__.py
Is is passed to dbconection.ConnectionURIOpener.registerConnection(),
and there it dies because SQLObject doesn't use it further. It
On Thu, Nov 27, 2008 at 4:44 PM, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>
> I think, though, that such a change should be applied to the trunk, not
> to the bugfix-only branches.
OK, I don't mind since I use a patched version in the meantime.
However, I wonder about the code in the isSupport
On Thu, Nov 27, 2008 at 04:35:43PM +0100, Markus Gritsch wrote:
> currently the sqlite3 module is, if present, preferred over a manually
> installed pysqlite2 module. Therefore it is not possible to use a
> newer version of pysqlite than the one that ships with Python 2.5 and
> 2.6. Is this reall
Hi,
currently the sqlite3 module is, if present, preferred over a manually
installed pysqlite2 module. Therefore it is not possible to use a
newer version of pysqlite than the one that ships with Python 2.5 and
2.6. Is this really the desired behavior?
The attached patch reverses the order in w
11 matches
Mail list logo
