Data integrity problem with sqlite3

Chris Angelico rosuav at
Tue Aug 11 14:44:06 CEST 2015

On Tue, Aug 11, 2015 at 10:37 PM, Frank Millman <frank at> wrote:
> My PostgreSQL is inaccessible at the moment as I am moving machines around,
> but I have tested it with MS SQL Server, and it behaves as expected – the
> transaction is fully rolled back and nothing is committed to the database.

Does MS SQL offer any hints in its logs? Can you enable full statement
logging, and then grep it for anything that doesn't begin INSERT or

> BTW, I am not using sqlite3 ‘in production’. Rather, I offer a choice of 3
> databases to my users – PostgreSQL, SQL Server, and sqlite3, so I have to
> make sure that my program works with all of them.

Ah. Comes to the same thing, anyway; if you can't get enough info out
of one backend, verify it with the others.


More information about the Python-list mailing list