On Tue, May 9, 2017 at 3:02 PM, Simon Slavin <[email protected]> wrote:
> On 9 May 2017, at 7:23am, Gwendal Roué <[email protected]> wrote: > > 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. > > Aren't triggers compiled into statements themselves? In that case, if authorizers are called on the full statement, I don't see why it wouldn't work. > I don’t think the authorisation system can be efficiently used in this > way. If you’re analysing statements speculatively you’ll get more > information out of EXPLAIN. On the contrary, a few months bad I was machine-parsing EXPLAIN, and was told to use authorizers instead. So it's probably completely appropriate, and I don't see why it wouldn't be efficient. --DD _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
