Re: [sqlite] A Descending Auto Increment Key

2017-07-20 Thread Don V Nielsen
On the heel of this is a grammatical error: "declared type "INTEGER" includes an "PRIMARY KEY DESC" clause". It should read "includes a "primary...". On Wed, Jul 19, 2017 at 11:03 PM, Keith Medcalf wrote: > > AUTOINCREMENT can only be used with INTEGER PRIMAY KEY columns in

Re: [sqlite] Possible inaccuracy in "Isolation In SQLite" paper

2017-07-20 Thread Olivier Mascia
> Le 20 juil. 2017 à 10:23, Olivier Mascia a écrit : > >> Le 20 juil. 2017 à 07:34, Rowan Worth a écrit : >> >> IMMEDIATE would take a RESERVED lock which is clearly not desired in this >> case -- the reader only wants a SHARED lock so as to minimise

Re: [sqlite] Possible inaccuracy in "Isolation In SQLite" paper

2017-07-20 Thread Gwendal Roué
> Le 20 juil. 2017 à 08:45, Clemens Ladisch a écrit : > > Rowan Worth wrote: >> On 18 July 2017 at 21:43, David Raymond wrote: >>> You can run "begin deferred transaction" then walk away for 3 months >>> without upsetting anything. If you need the

Re: [sqlite] Possible inaccuracy in "Isolation In SQLite" paper

2017-07-20 Thread Olivier Mascia
> Le 20 juil. 2017 à 07:34, Rowan Worth a écrit : > > IMMEDIATE would take a RESERVED lock which is clearly not desired in this > case -- the reader only wants a SHARED lock so as to minimise contention > with the writer. This discussion revolved around WAL mode. BEGIN

Re: [sqlite] Possible inaccuracy in "Isolation In SQLite" paper

2017-07-20 Thread Clemens Ladisch
Rowan Worth wrote: > On 18 July 2017 at 21:43, David Raymond wrote: >> You can run "begin deferred transaction" then walk away for 3 months >> without upsetting anything. If you need the precise timing then why not >> just use "begin immediate"? > > IMMEDIATE would take