> Le 9 mai 2017 à 15:41, Gwendal Roué <gwendal.r...@gmail.com> a écrit : > >>> As a reminder, I intend to use the authorisation system in order to tell if >>> a statement has an opportunity to impact on another statement, as a support >>> for a general database observation feature. >> >> How are you going to handle TRIGGERs ? The authoriser analyses each >> statement individually. It will not tell you everything that’s in the >> TRIGGER until it decides to execute those statements. > > That's a very good question.
Very good news: foreign keys and triggers are 100% handled by authorizer callbacks, for free :-D How much a boon is SQLite, frankly ??? Look: CREATE TABLE table1 ( ... ); CREATE TABLE table2 ( ... ); CREATE TRIGGER trigger1 AFTER INSERT ON table2 BEGIN DELETE FROM table1; END; INSERT INTO table2 (id) VALUES (NULL); -- SQLITE_INSERT table2 main -- SQLITE_DELETE table1 main trigger1 :-) Gwendal Roué _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
