On May 30, 8:43 am, "Stefan Sonnenberg-Carstens"
<[EMAIL PROTECTED]> wrote:
> Did you try a commit() ?
>
> SQLite3 works in autocommit mode by default,
E IF it worked in auto-commit mode, then the OP wouldn't
need to use Connection.commit(-:)
The underlying SLQite3 may work in auto-c
On 5/29/07, Stefan Sonnenberg-Carstens
<[EMAIL PROTECTED]> wrote:
> Did you try a commit() ?
>
> SQLite3 works in autocommit mode by default,
> so it would help to see your code.
>
>
> On Mi, 30.05.2007, 00:30, Chris Fonnesbeck wrote:
> > I have a script set up to perform UPDATE commands on an sqli
Did you try a commit() ?
SQLite3 works in autocommit mode by default,
so it would help to see your code.
On Mi, 30.05.2007, 00:30, Chris Fonnesbeck wrote:
> I have a script set up to perform UPDATE commands on an sqlite database
> using the sqlite3 module. Everything appears to run fine (there a
Chris Fonnesbeck wrote:
> I have a script set up to perform UPDATE commands on an sqlite database
> using the sqlite3 module. Everything appears to run fine (there are no
> error messages), except that none of the UPDATE commands appear to have
> actually updated the table. If I run each command
I have a script set up to perform UPDATE commands on an sqlite database
using the sqlite3 module. Everything appears to run fine (there are no error
messages), except that none of the UPDATE commands appear to have actually
updated the table. If I run each command on its own in a sqlite session, t
