Igor wrote:
" On 9/8/2016 1:15 PM, Stephan Mueller wrote:
" > " > I'd prefer to commit after each update
" > " You can't commit on a single connection either, while there's an
" > " unfinalized SELECT statement traversal going on. So you aren't gaining
" > " anything by trying to interleave SELECT
On 9/8/2016 1:15 PM, Stephan Mueller wrote:
" > I'd prefer to commit after each update
" You can't commit on a single connection either, while there's an
" unfinalized SELECT statement traversal going on. So you aren't gaining
" anything by trying to interleave SELECT and updates on the same conn
,
stephan();
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Keith Medcalf
Sent: Wednesday, September 07, 2016 7:15 PM
To: SQLite mailing list
Subject: Re: [sqlite] Clarification on "No Isolation On Same Db Connection"
d.
stephan();
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Kevin O'Gorman
Sent: Thursday, September 08, 2016 10:07 AM
To: SQLite mailing list
Subject: Re: [sqlite] Clarification on "No Isolation On Same Db Connection&
Igor wrote:
" On 9/7/2016 6:11 PM, Stephan Mueller wrote:
" > I understand that a way to ensure "SELECT is unperturbed" semantics is to
" > use separate connections for SELECT and updates.
" If you go down that route, make sure you are using WAL journaling mode;
" it won't work otherwise.
I see t
s.sqlite.org
Subject: [sqlite] Clarification on "No Isolation On Same Db Connection"
Hello all;
I have a scenario that is well covered by the text at
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.sqlite.org%2fisolation.html&data=02%7c01
It seems to me that the simplest, most portable approach for this sort of
thing would to be having the SELECT create a temporary table of the desired
actions, and not apply them until after the select has concluded. This
would work in any database -- it does not depend on precise semantics of
WAL,
On 9/7/2016 6:11 PM, Stephan Mueller wrote:
I understand that a way to ensure "SELECT is unperturbed" semantics is to use
separate connections for SELECT and updates.
If you go down that route, make sure you are using WAL journaling mode;
it won't work otherwise.
This is undesirable since
n Mueller
> Sent: Wednesday, 7 September, 2016 16:12
> To: sqlite-users@mailinglists.sqlite.org
> Subject: [sqlite] Clarification on "No Isolation On Same Db Connection"
>
> Hello all;
>
> I have a scenario that is well covered by the text at
> https://www.sqlite.org/iso
ot;No Isolation On Same Db Connection"
Hello all;
I have a scenario that is well covered by the text at
https://www.sqlite.org/isolation.html in the section "No Isolation Between
Operations On The Same Database Connection" (relevant paragraphs at end for
convenience) but am hoping fo
Hello all;
I have a scenario that is well covered by the text at
https://www.sqlite.org/isolation.html in the section "No Isolation Between
Operations On The Same Database Connection" (relevant paragraphs at end for
convenience) but am hoping for a bit more clarity. Here's an overview of my
s
11 matches
Mail list logo