Re: [SQLObject] dburi argument handling fixes

2008-09-10 Thread Dan Pascu
On Wednesday 10 September 2008, Oleg Broytmann wrote: > On Wed, Sep 10, 2008 at 03:57:45PM +0300, Dan Pascu wrote: > > On Wednesday 10 September 2008, Oleg Broytmann wrote: > > > > The second fix is for incorrectly interpretted boolean values > > > > passed via arguments to connectionForURI or via

Re: [SQLObject] dburi argument handling fixes

2008-09-10 Thread Oleg Broytmann
On Wed, Sep 10, 2008 at 03:57:45PM +0300, Dan Pascu wrote: > On Wednesday 10 September 2008, Oleg Broytmann wrote: > > > The second fix is for incorrectly interpretted boolean values passed > > > via arguments to connectionForURI or via dburi parameters. > > > >Why Boolean is a class and not ju

Re: [SQLObject] dburi argument handling fixes

2008-09-10 Thread Dan Pascu
On Wednesday 10 September 2008, Oleg Broytmann wrote: > > The second fix is for incorrectly interpretted boolean values passed > > via arguments to connectionForURI or via dburi parameters. > >Why Boolean is a class and not just a function? It never creates any > instance of the class. No part

Re: [SQLObject] dburi argument handling fixes

2008-09-10 Thread Oleg Broytmann
Hello! On Wed, Sep 10, 2008 at 03:02:54PM +0300, Dan Pascu wrote: > I just commited some fixes regarding how the dburi parameters are handled. I am blessing both of them. Thank you for the job! > The second fix is for incorrectly interpretted boolean values passed via > arguments to connecti

[SQLObject] dburi argument handling fixes

2008-09-10 Thread Dan Pascu
I just commited some fixes regarding how the dburi parameters are handled. The first fix is for incorrect handling of calls like connectionForURI(dburi, cache=False) when dburi already contains some parameters encoded in the URI, like mysql://user:[EMAIL PROTECTED]/db?debug=1 The second fix