Re: [sqlite] Trigger Performance

2018-06-12 Thread Space Pixel
I'll try to do whatever I can. On Tue, Jun 12, 2018, 8:10 PM Simon Slavin wrote: > On 12 Jun 2018, at 10:49am, Space Pixel wrote: > > > the console > > shows a warning, about an inappropriate loader to some C# file. > > There is no C# code in SQLite. It's all plain C. Can you show us the > er

Re: [sqlite] Trigger Performance

2018-06-12 Thread Simon Slavin
On 12 Jun 2018, at 10:49am, Space Pixel wrote: > the console > shows a warning, about an inappropriate loader to some C# file. There is no C# code in SQLite. It's all plain C. Can you show us the error message and tell us how it relates to you using SQLite commands ? Simon. _

Re: [sqlite] Trigger Performance

2018-06-12 Thread Space Pixel
difference. > >>> > >>> --- > >>> The fact that there's a Highway to Hell but only a Stairway to > >Heaven says a lot about anticipated traffic volume. > >>> > >>> > >>>>-Original Message- > >>&

Re: [sqlite] Trigger Performance

2018-06-11 Thread Keith Medcalf
sers- >boun...@mailinglists.sqlite.org] On Behalf Of David Burgess >Sent: Monday, 11 June, 2018 17:50 >To: SQLite mailing list >Subject: Re: [sqlite] Trigger Performance > >Trying again/ >Specifically, preparation of the constant "trigger part" of the >statement is &g

Re: [sqlite] Trigger Performance

2018-06-11 Thread David Burgess
served difference. >> >> --- >> The fact that there's a Highway to Hell but only a Stairway to Heaven says a >> lot about anticipated traffic volume. >> >> >>>-Original Message----- >>>From: sqlite-users [mailto:sqlite-users- >>>boun...@mailing

Re: [sqlite] Trigger Performance

2018-06-11 Thread David Burgess
mailinglists.sqlite.org] On Behalf Of David Burgess >>Sent: Monday, 11 June, 2018 00:40 >>To: SQLite mailing list >>Subject: Re: [sqlite] Trigger Performance >> >>> The trigger is adding a mere 10% overhead on a million rows ... >>3.24 on a real data DB (16 colum

Re: [sqlite] Trigger Performance

2018-06-11 Thread Keith Medcalf
sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of David Burgess >Sent: Monday, 11 June, 2018 00:40 >To: SQLite mailing list >Subject: Re: [sqlite] Trigger Performance > >> The trigger is adding a mere 10% overhead on a million rows ... >3.24 on a real da

Re: [sqlite] Trigger Performance

2018-06-10 Thread David Burgess
> The trigger is adding a mere 10% overhead on a million rows ... 3.24 on a real data DB (16 columns), the inserts were generated from .dump in the shell, about 45MB of input data so BEGIN; lots of inserts COMMIT; Run on a laptop i7 with SSD (not that should make any difference to the relative p

Re: [sqlite] Trigger Performance

2018-06-10 Thread Keith Medcalf
Interesting. That is adding 30% or so to process the trigger. When I do (this is to a "memory" database): SQLite version 3.25.0 2018-06-11 01:30:03 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> creat