Thanks for asking your crystal ball. it works rather well. --- On Tue, 6/2/09, Igor Tandetnik <[email protected]> wrote:
> From: Igor Tandetnik <[email protected]> > Subject: Re: [sqlite] Before Update trigger question > To: [email protected] > Date: Tuesday, June 2, 2009, 2:48 PM > Boris Ioffe <[email protected]> > wrote: > > --- On Tue, 6/2/09, Igor Tandetnik > > <[email protected]> > wrote: > > > >> From: Igor Tandetnik <[email protected]> > >> Subject: Re: [sqlite] Before Update trigger > question > >> To: [email protected] > >> Date: Tuesday, June 2, 2009, 2:11 PM > >> Boris Ioffe <[email protected]> > >> wrote: > >>> This is my first question on this mail list. I > noticed > >> that BEFORE > >>> UPDATE trigger goes off even for insert > statements. > >> > >> My crystal ball shows you have an INSERT trigger > that > >> performs an > >> UPDATE. > > > > Very intrigued. You ruined some sql foundational > priciples I lived > > upon. How is it possible for insert statement to > update? Even replace > > is (delete on constraint then insert). Can you > elaborate your answer > > a bit ? > > CREATE TRIGGER players_insert AFTER INSERT ON players > BEGIN > UPDATE players ...; > END; > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
