On Wednesday 14 June 2006 17:47, Oleg Broytmann wrote:
> On Wed, May 31, 2006 at 03:18:38PM +0300, Dan Pascu wrote:
> > -opts['timeout'] = float(popKey(kw, 'timeout'))
> > +if using_sqlite2:
> > +opts['timeout'] = float(popKey(kw, 'timeout'))
> > +
On Wed, May 31, 2006 at 03:18:38PM +0300, Dan Pascu wrote:
> -opts['timeout'] = float(popKey(kw, 'timeout'))
> +if using_sqlite2:
> +opts['timeout'] = float(popKey(kw, 'timeout'))
> +else:
> +opts['timeout'] = int(float(popKey(kw,
On Wed, May 31, 2006 at 03:18:38PM +0300, Dan Pascu wrote:
> The attached patch fixes the issue and also unifies how the timeout is
> specified for sqlite connections. The timeout parameters in sqlobject
> will always be in seconds and internally will be sent as the integer
> number of milliseco
When I specify a timeout for a sqlite connection that uses the older
sqlite db module I get the following warning:
/usr/lib/python2.3/site-packages/sqlite/main.py:472: DeprecationWarning:
integer argument expected, got float
self.db.sqlite_busy_timeout(timeout)
This is because the older sqli
