Jonathan Wight wrote:
> Actually it obviously isn't a cherrypy issue - I was getting two
> problems mixed up. The sqlite I am linking to is compiled with --
> threadsafe and hasn't changed since the last time i upgraded turbogears.
Some comments from the pysqlite author ;-)
"Something" is trying to execute more than one statement with
cursor.execute or cursor.executemany. Since this is against the
specified semantics of these API calls as per the DB-API, checks were
added to raise errors:
>>> from pysqlite2 import dbapi2 as sqlite
>>> con = sqlite.connect(":memory:")
>>> cur = con.cursor()
>>> cur.execute("select 4+5;")
<pysqlite2.dbapi2.Cursor object at 0x00BA1E60>
>>> cur.execute("select 4+5; ")
<pysqlite2.dbapi2.Cursor object at 0x00BA1E60>
>>> cur.execute("select 4+5; -- bla bla")
<pysqlite2.dbapi2.Cursor object at 0x00BA1E60>
>>> cur.execute("create table foo(bar); create table baz(zippo);")
Traceback (most recent call last):
File "<stdin>", line 1, in ?
pysqlite2.dbapi2.Warning: You can only execute one statement at a time.
>>> cur.executescript("create table foo(bar); create table baz(zippo);")
<pysqlite2.dbapi2.Cursor object at 0x00BA1E60>
I. e. *if* anybody *really* needs this functionality, there is a
nonstandard executescript() method in pysqlite.
It smells like a SQLObject-related thing to me.
-- Gerhard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
