Re: custom sql with sqlite causes backtrace

2009-04-18 Thread Tim Chase
> Warning: You can only execute one statement at a time. ... > cursor.execute(""" > BEGIN; > UPDATE clients > SET connected = 'false' > WHERE connected = 'true' > AND tugid <> %s; > COMMIT;""", [local_tugid]) > > Am I

Re: custom sql with sqlite causes backtrace

2009-04-18 Thread msoulier
On Apr 18, 1:42 pm, msoulier wrote: >         cursor.execute(""" >             BEGIN; >             UPDATE clients >             SET connected = 'false' >             WHERE connected = 'true' >             AND tugid <> %s; >             COMMIT;""", [local_tugid]) And, of course, just after posti

custom sql with sqlite causes backtrace

2009-04-18 Thread msoulier
My production code is using Python 2.3 and Django 0.96. Yes, I know. Next release picks up Django 1.0.2 and Python 2.4. Yay. In the meantime, I have a custom model manager with a method that executes custom sql. Works fine with PostgreSQL, but when I'm developing with SQLite I get a traceback. T