"Frank Millman" wrote in message news:mqcslv$tee$1...@ger.gmane.org...
"Frank Millman" wrote in message news:mqcmie$po9$1...@ger.gmane.org...
> Hi all
>
> I have a 'data integrity' problem with sqlite3 that I have been battling
> with for a while.
"Frank Millman" wrote in message news:mqcmie$po9$1...@ger.gmane.org...
Hi all
I have a 'data integrity' problem with sqlite3 that I have been battling
with for a while. I have not got to the bottom of it yet but I do have
some useful info, so I thought I would post it h
On Tue, Aug 11, 2015 at 10:37 PM, Frank Millman 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
"Chris Angelico" wrote in message
news:CAPTjJmrHmj2bsdSm4CQ=orgxutmyctk3w3e3n-qxolg2tvq...@mail.gmail.com...
On Tue, Aug 11, 2015 at 9:33 PM, Frank Millman wrote:
> I have added 'set_trace_callback' to see exactly what is going on, and
> in
> the middle of my series of commands I find the fo
On Tue, Aug 11, 2015 at 9:33 PM, Frank Millman wrote:
> I have added 'set_trace_callback' to see exactly what is going on, and in
> the middle of my series of commands I find the following -
>
>COMMIT
>BEGIN IMMEDIATE
>
> According to the docs, the sqlite3 module commits transactions impli
Hi all
I have a 'data integrity' problem with sqlite3 that I have been battling
with for a while. I have not got to the bottom of it yet but I do have some
useful info, so I thought I would post it here in the hope that someone with
some knowledge of the internals of the python sqli
