Re: [sqlite] Re: Re: trigger and new.*

[Charly Caulet]

Le mercredi 11 juillet 2007 à 12:47 -0400, Igor Tandetnik a écrit :
> Be aware that SQLite never enters infinite loop of triggers. It keeps 
> track of a chain of nested triggers that led to the currently executing 
> statement; if that statement would fire a trigger that is already in the 
> chain, the trigger does not run.
> 
> Notice how, in my solution, a BEFORE INSERT trigger runs an INSERT on 
> the same table, with no ill effects.
Yes... So I don't know why but only with 4 triggers, I made my database
become very slow. On some requests, it was "calculating" while 10 sec,
and after an core dump happends...
-- 
Charly CAULET

membre de www.208assistance.org
ID jabber : [EMAIL PROTECTED]
clé gpg : 0x7DE10F3C (pgp.mit.edu)


signature.asc
Description: Ceci est une partie de message	numériquement signée

[sqlite] Re: Re: trigger and new.*

[Igor Tandetnik]

Charly Caulet <[EMAIL PROTECTED]>
wrote:

I mean that I had a trigger on "INSERT" that executes an update, and
I had
some  triggers on "UPDATE" that executes any other updates... So it
was an
infernal loop.


Be aware that SQLite never enters infinite loop of triggers. It keeps 
track of a chain of nested triggers that led to the currently executing 
statement; if that statement would fire a trigger that is already in the 
chain, the trigger does not run.


Notice how, in my solution, a BEFORE INSERT trigger runs an INSERT on 
the same table, with no ill effects.


Igor Tandetnik 



-
To unsubscribe, send email to [EMAIL PROTECTED]
-