On Sun, Sep 1, 2013 at 2:23 PM, Simon Slavin <slav...@bigfraud.org> wrote:
>
> On 1 Sep 2013, at 6:38pm, Richard Hipp <d...@sqlite.org> wrote:
>
> > A good starting place might be to tell us what the program is doing when
> > the error comes back.
>
> As well as telling us the call that trieggers the error, please put logic
> into your program so that it not only checks the result code of the call
> that generates the error but also checks to see that all earlier SQLite
> calls return SQLITE_OK when you expect them to. Often the call that
> returns the error is after the one that caused the problem.
>
Do you know how I can do that with Python? For example, I tried this:
status = cursor.execute("some SQL statement here")
print "The status is: ", status
But it prints the cursor object:
> The status is <sqlite3.Cursor object at 0x034313B0>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
