On Thu, 21 Feb 2013 10:32:51 -0800 (PST)
Peter Aronson wrote:
> an outer select loop was reading records, and an inner select loop
> was inserting records based on the records found into the same
> table.
For every row, this design requires 2 trips to the database. Besides
<slav...@bigfraud.org>
Date:
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Subject: Re: [sqlite] Ongoing SELECT sees INSERTed rows.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi
On 21 Feb 2013, at 6:56pm, Peter Aronson wrote:
> Thanks! The possibility we were wondering about was having an integer
> primary
> key autoincrement column and just exiting the select loop when encountering a
> id
> greater than the max id at start time (I assume this
- Original Message
> From: Richard Hipp <d...@sqlite.org>
> To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
> Sent: Thu, February 21, 2013 11:39:44 AM
> Subject: Re: [sqlite] Ongoing SELECT sees INSERTed rows.
>
> On Thu, Feb 21, 2013 at
On Thu, Feb 21, 2013 at 1:32 PM, Peter Aronson wrote:
> SQLite 3.7.15.2, Solaris and Windows (and presumably others). Journal
> mode is
> delete, but WAL appears to behave in the same manner.
>
> One of my coworkers ran into an infinite loop when accessing SQLite.
>
SQLite 3.7.15.2, Solaris and Windows (and presumably others). Journal mode is
delete, but WAL appears to behave in the same manner.
One of my coworkers ran into an infinite loop when accessing SQLite.
Essentially
an outer select loop was reading records, and an inner select loop was
6 matches
Mail list logo