On 5 Mar 2019, at 3:22am, Rowan Worth wrote:
> Wait what? If I've understood correctly you're describing a situation where
> statements outlive their transaction context?
The documentation on transactions covers this possibility. This includes
continuing to do _step() for one statement while
On Monday, 4 March, 2019 20:23, Rowan Worth wrote:
>On Sun, 3 Mar 2019 at 20:53, Keith Medcalf wrote:
>> Statements which were in progress that were permitted to proceed
>> (ie, where the next step did not return an abort error) continue
>> with a read lock in place (ie, as if they were part o
On Sun, 3 Mar 2019 at 20:53, Keith Medcalf wrote:
> My observation (on the current tip version 3.28.0) of Schrodingers
> Transactions is that if there is (for example) a transaction in progress
> and that is COMMIT or ROLLBACK, then the changes are either committed or
> rolled back and the explic
On 3-3-2019 16:27, Jesse Rittner wrote:
It didn't work correctly because the sequence of commands you sent doesn't
make sense.
BEGIN;
...
RELEASE point1;
...
ROLLBACK;
...
END;
First you began an explicit transaction. Then you tried to release a
savepoint that you never created. (Hence the "no
It didn't work correctly because the sequence of commands you sent doesn't
make sense.
BEGIN;
...
RELEASE point1;
...
ROLLBACK;
...
END;
First you began an explicit transaction. Then you tried to release a
savepoint that you never created. (Hence the "no such savepoint" error
message.) Then you
On 3-3-2019 15:33, Simon Slavin wrote:
On 3 Mar 2019, at 2:29pm, Luuk wrote:
Conclusion: RESTORE does not end TRANSACTION ?
Your statement is correct. However, RESTORE is a partner of SAVEPOINT. My
question does not consider SAVEPOINTs.
Simon.
On 3 Mar 2019, at 2:29pm, Luuk wrote:
> Conclusion: RESTORE does not end TRANSACTION ?
Your statement is correct. However, RESTORE is a partner of SAVEPOINT. My
question does not consider SAVEPOINTs.
Simon.
___
sqlite-users mailing list
sqlite-user
On 3-3-2019 15:01, Richard Damon wrote:
On Mar 3, 2019, at 8:32 AM, Simon Slavin wrote:
To summarize, the list feels that this is an incorrect model
BEGIN;
... first set of commands
ROLLBACK;
... second set of commands
END;
whereas this is how things are meant to work:
On Mar 3, 2019, at 8:32 AM, Simon Slavin wrote:
>
> To summarize, the list feels that this is an incorrect model
>
>BEGIN;
>... first set of commands
>ROLLBACK;
>... second set of commands
>END;
>
> whereas this is how things are meant to work:
>
>BEGIN;
>... first
To summarize, the list feels that this is an incorrect model
BEGIN;
... first set of commands
ROLLBACK;
... second set of commands
END;
whereas this is how things are meant to work:
BEGIN;
... first set of commands
ROLLBACK;
BEGIN;
... second set of comman
irway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Saturday, 2 March, 2019 19:52
>To: SQLite mailing list
>Subject: Re: [sq
2 March, 2019 19:32
>To: SQLite mailing list
>Subject: Re: [sqlite] Handling ROLLBACK
>
>
>>Suppose ROLLBACK does not cancel the BEGIN, can a programmer
>reliably
>>issue more SQL commands, including another ROLLBACK ? Will SQLite
>>continue to react correctly to
>Suppose ROLLBACK does not cancel the BEGIN, can a programmer reliably
>issue more SQL commands, including another ROLLBACK ? Will SQLite
>continue to react correctly to other ROLLBACKs, and to SQL commands
>which result in "(516) SQLITE_ABORT_ROLLBACK".
A successful ROLLBACK on a transaction di
ay to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin
>Sent: Saturday, 2 March, 2019 16:12
>To: SQLite mailing list
>Subject: [sq
No
On Sat, Mar 2, 2019, 18:50 D Burgess wrote:
> Does ROLLBACK release the transaction lock on the database ?
>
> I checked scripts on this. Yes.
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.or
Does ROLLBACK release the transaction lock on the database ?
I checked scripts on this. Yes.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
if I understand the question:
On Sun, Mar 3, 2019 at 10:12 AM Simon Slavin wrote:
> Does ROLLBACK release the transaction lock on the database ?
>
I think so or my code would not be working.
>
> Does ROLLBACK cancel the BEGIN ? Or do I need to issue END ?
>
END is a synonym for commit . So
beg
I have run experiments in the shell tool, using different journal modes, but I
would like to know whether my observations are cannon or just one-offs.
Contributions welcome from all, especially those who have read SQLite source
code, and SQL language-lawyers whether or not you're familiar with
18 matches
Mail list logo
