On Wed, Jul 26, 2017 at 12:16 PM, Clemens Ladisch wrote:
> Igor Korot wrote:
>> If I execute "BEGIN TRANSACTION" and for whatever reason the call will fail
>> will I get an error on COMMIT/ROLLBACK execution?
>
> sqlite> begin immediate;
> Error: database is locked
> sqlite> rollback;
> Error:
Igor Korot wrote:
> If I execute "BEGIN TRANSACTION" and for whatever reason the call will fail
> will I get an error on COMMIT/ROLLBACK execution?
sqlite> begin immediate;
Error: database is locked
sqlite> rollback;
Error: cannot rollback - no transaction is active
Regards,
Clemens
Hi, ALL,
If I execute "BEGIN TRANSACTION" and for whatever reason the call will fail
will I get an error on COMMIT/ROLLBACK execution?
This is an un-named transaction and it is an outmost one.
Thank you.
___
sqlite-users mailing list
sqlite-users@maili
Thank you both for your answers. I am using the shared memory segment in
application startup approach. It seems that the problem was with allocating
memory for an iterator to my data structure each time on xOpen and freeing the
memory on xClose. It seems that for one thread it was not a big issu
On 07/25/2017 08:42 PM, Bubu Bubu wrote:
I'm having trouble with foreign key constraints et cascade clauses and I
don't really know where could be the problem.
I'm working on sqlite version 3.8.11.1 (I can't update it, work
restriction), but I checked and such functionnalities are enabled (correc
I'm having trouble with foreign key constraints et cascade clauses and I
don't really know where could be the problem.
I'm working on sqlite version 3.8.11.1 (I can't update it, work
restriction), but I checked and such functionnalities are enabled (correct
me if I'm wrong).
I've renamed everythin
6 matches
Mail list logo