Perhaps I need to be more explicit:
If the transaction fails because of a constraint violation, then using either
the ROLLBACK, IGNORE, or REPLACE conflict resolution strategies would commit or
roll back the transaction and automatically close it. If you add conflict
clauses to table schemata, it wouldn't even require changes to the logic of
On October 4, 2017 10:20:01 PM EDT, Igor Korot <ikoro...@gmail.com> wrote:
>On Wed, Oct 4, 2017 at 6:19 PM, J. King <jk...@jkingweb.ca> wrote:
>> See also:
>This is good to know but I don't think it is applicable in this case
>as I explicitly said
>that this is inside transaction which fails.
>> On October 4, 2017 6:15:55 PM EDT, Jens Alfke <j...@mooseyard.com>
>>>> On Oct 4, 2017, at 2:20 PM, Igor Korot <ikoro...@gmail.com> wrote:
>>>> If I start transaction, all queries were successful, but issuing
>>>> On such failure I am going to present an error, but then what
>>>> if I go and try to close the connection?
>>>If COMMIT fails, you should execute a ROLLBACK to abort the
>>>transaction, then continue with failure handling. Otherwise yes, the
>>>transaction remains open and will cause trouble when you try to close
>>>sqlite-users mailing list
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> sqlite-users mailing list
>sqlite-users mailing list
Sent from my Android device with K-9 Mail. Please excuse my brevity.
sqlite-users mailing list