Re: [sqlite] Trigger slowness even when it's not fired

sh > Symington > Gesendet: Montag, 04. Juli 2016 11:29 > An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Betreff: Re: [sqlite] Trigger slowness even when it's not fired > > Hi there, > >> How many times are you preparing the update statement? Maybe you a

Re: [sqlite] Trigger slowness even when it's not fired

On Mon, Jul 4, 2016 at 1:18 PM, R Smith wrote: > On 2016/07/04 1:13 PM, Dominique Devienne wrote: > >> On Mon, Jul 4, 2016 at 12:08 PM, Hick Gunter wrote: >> >>> A simple UPDATE set = where will >>> translate into about 40 instructions; adding your

Re: [sqlite] Trigger slowness even when it's not fired

On 2016/07/04 1:13 PM, Dominique Devienne wrote: On Mon, Jul 4, 2016 at 12:08 PM, Hick Gunter wrote: A simple UPDATE set = where will translate into about 40 instructions; adding your trigger adds an additional estimated 400 instructions of trigger program. But the

Re: [sqlite] Trigger slowness even when it's not fired

On Mon, Jul 4, 2016 at 12:08 PM, Hick Gunter wrote: > Creating a trigger causes SQLite to insert a row into the sqlite_master > table which contains the text you supply for the trigger. No code is > generated at this time. You can verify this by creating a trigger that >

Re: [sqlite] Trigger slowness even when it's not fired

sts.sqlite.org> Betreff: Re: [sqlite] Trigger slowness even when it's not fired Hi there, > How many times are you preparing the update statement? Maybe you are just > measuring the effort required to prepare 55000 UPDATE statements. OK, this sounds plausible. But given the tri

Re: [sqlite] Trigger slowness even when it's not fired

glists.sqlite.org] Im Auftrag von Hamish > Symington > Gesendet: Montag, 04. Juli 2016 10:27 > An: sqlite-users@mailinglists.sqlite.org > Betreff: [sqlite] Trigger slowness even when it's not fired > > Hello, > > I have a curious situation involving a trigger, which I’m at a lo

Re: [sqlite] Trigger slowness even when it's not fired

On Mon, Jul 4, 2016 at 10:26 AM, Hamish Symington < ham...@lightbluesoftware.com> wrote: > [...] If I remove all of the UPDATE rows from this trigger, and make no > other changes, the test takes approximately 12 seconds. > I don’t understand why removing code from the body of a trigger which >

Re: [sqlite] Trigger slowness even when it's not fired

...@mailinglists.sqlite.org] Im Auftrag von Hamish Symington Gesendet: Montag, 04. Juli 2016 10:27 An: sqlite-users@mailinglists.sqlite.org Betreff: [sqlite] Trigger slowness even when it's not fired Hello, I have a curious situation involving a trigger, which I’m at a loss to explain. I’m wondering if someone who

Re: [sqlite] Trigger slowness even when it's not fired

Hi there, > > It's known that triggers aren't SQLite most remarkable strength, even if I > never encountered a situation where their relative slowness significantly > exceeds their usefulness. > In your situation I believe your coumpond triggering condition needs > parenthesis. Your

Re: [sqlite] Trigger slowness even when it's not fired

At 10:26 04/07/2016, you wrote: Hello, I have a curious situation involving a trigger, which I’m at a loss to explain. I’m wondering if someone who knows more about the insides of SQLite can tell me more about why it’s happening. I’m running SQLite 3.8.7. The trigger code is at

[sqlite] Trigger slowness even when it's not fired

Hello, I have a curious situation involving a trigger, which I’m at a loss to explain. I’m wondering if someone who knows more about the insides of SQLite can tell me more about why it’s happening. I’m running SQLite 3.8.7. The trigger code is at the bottom of this email. It’s a