I have a TurboGears application using SQLObject, and upgraded from
SQLite 3.2.1 to 3.3.4 to see if it would solve a performance problem
[1]. Instead I get an exception (below) whenever I hit a page that
does any query. If I downgrade SQLite, the old behavior returns. I'm
using SQLObject 0.7.1dev
On Wed, Mar 08, 2006 at 03:06:25PM +0100, David Faure wrote:
> Hmm, the last line shouldn't have been added, since the support for '%s'
> hasn't been committed.
>
> --- docs/SQLObject.txt (revision 1634)
> +++ docs/SQLObject.txt (working copy)
> @@ -739,7 +739,6 @@ values are:
> single SQL
On Tuesday 21 February 2006 15:32, David Faure wrote:
> SQLObject currently assumes that a default database was selected for the
> connection.
> However I'm using SQLObject in a C++ application which executes python
> scripts,
> and the connection doesn't have a default database selected, on purp
On Sunday 26 February 2006 16:46, Oleg Broytmann wrote:
> On Wed, Feb 22, 2006 at 01:21:58AM +0100, David Faure wrote:
> > +`createSQL`:
> > + SQL queries run after table creation. createSQL can be a string with a
> > + single SQL command, a list of SQL commands, or a dictionary with keys
> >
