On 20 Nov 2011, at 5:04am, Matt Young wrote: >> sqlite> drop trigger if exists mytrigger; >> sqlite> create trigger mytrigger after insert on result >> ...> begin >> ...> select 'Test2'; >> ...> end; >> sqlite> insert into result values(0,0,0); >> sqlite> >> >> Explain the path of select here?
> Well, it was listed as an initial option o the trigger, so I didn't quite > get it either. You generally use TRIGGERs to make changes to the database. They're for things like making sure an author record exists for every book you have. Or for keeping account balances updated. That stuff. Although it's not a violation of the syntax, a SELECT in a TRIGGER doesn't report its results to anything. The only reason I can think of for doing one is it uses a function that has some weird side-effect. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
