On sqlite-users@mailinglists.sqlite.org, Randall Smith
wrote:
>Date: Fri, 23 Aug 2019 13:16:18 +0100
>From: Simon Slavin mailto:slav...@bigfraud.org>>
>>I have no connection with this extension to the APSW Python SQLite
>>wrapper, I just saw a pointer to it. The latest commit is around
Date: Fri, 23 Aug 2019 13:16:18 +0100
From: Simon Slavin mailto:slav...@bigfraud.org>>
I have no connection with this extension to the APSW Python SQLite wrapper, I
just saw a pointer to it. The latest commit is around nine months ago.
Perhaps someone who is familiar with Python libraries
Hi!
On 26.08.19 14:05, Simon Slavin wrote:
> On 26 Aug 2019, at 12:43pm, Dan Kennedy wrote:
>> When sqlite3changeset_apply() hits a UNIQUE constraint, it puts the change
>> into a "retry buffer". Then, once it has attempted all changes in the
>> changeset, it goes back and retries those in the
On 26 Aug 2019, at 12:43pm, Dan Kennedy wrote:
> When sqlite3changeset_apply() hits a UNIQUE constraint, it puts the change
> into a "retry buffer". Then, once it has attempted all changes in the
> changeset, it goes back and retries those in the retry buffer. It keeps
> retrying like this
On 26/8/62 15:12, Daniel Kraft wrote:
Hi!
I'm using the SQLite session extension to create changesets, invert them
and apply them to undo previous changes in the database. (Essentially
what I need to do is persistent savepoints.)
This works well so far, but I recently wondered about the
Hi!
I'm using the SQLite session extension to create changesets, invert them
and apply them to undo previous changes in the database. (Essentially
what I need to do is persistent savepoints.)
This works well so far, but I recently wondered about the interaction
with UNIQUE constraints. In
Why would you want to do this?
If you require a SELECT to return rows in a certain order, you need to specify
ORDER BY on the SELECT statement. And not rely on ascending insert time or any
other visitation order effect.
Additionally - unless specific precautions are taken - sorted insert
I think you are looking for UNION ALL to avoid creating an ephemeral table to
implement the implied DISTINCT
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Peter da Silva
Gesendet: Donnerstag, 22. August 2019 17:28
An:
8 matches
Mail list logo