Note that parsing debug output is not a stable method of analysis (meaning
SQlite Dev can change anything at whim), whereas the authorizer interface is
documented.
Your implicit claim is "not all instances of column reference are reported to
the authorizer, notably those inside a USING clause".
The following simple example might illustrate what I’m trying to achieve
CREATE TABLE tbl0 (a INTEGER PRIMARY KEY, b INTEGER);
CREATE TABLE tbl1 (a INTEGER PRIMARY KEY, c INTEGER);
Suppose a user enters the following sql
SELECT b, c FROM tbl0 INNER JOIN tbl1 USING (a) WHERE a > ?1;
I want to sc
Thanks Gunter. I didn’t include the text of the original SELECT as it was
basically an unnecessarily complex jumble of WITHs and embedded SELECTS just so
I could see the response of the TreeViewSelect. I hoped someone would’ve been
able to say “yes, the WITH is just included for completeness but
WITH is basically syntactic sugar that allows you to name the result set of a
certain select and refer to it by name, so that select has to appear in the
generated bytecode and also in the query resolution tree.
Guessing what an element of the query resolution tree does would be very much
easie
4 matches
Mail list logo
