Re: Data integrity problem with sqlite3

References	<mqcmie$po9$1@ger.gmane.org> <CAPTjJmrHmj2bsdSm4CQ=oRGxuTmycTk3W3e3n-QXoLg2TVQMbA@mail.gmail.com> <mqcqav$m0b$1@ger.gmane.org>
Date	2015-08-11 22:44 +1000
Subject	Re: Data integrity problem with sqlite3
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.81.1439297048.3627.python-list@python.org> (permalink)

Show all headers | View raw

On Tue, Aug 11, 2015 at 10:37 PM, Frank Millman <frank@chagford.com> 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
UPDATE or SELECT?

> 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.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Data integrity problem with sqlite3 Chris Angelico <rosuav@gmail.com> - 2015-08-11 22:44 +1000

csiph-web