On Sat, Mar 17, 2018 at 11:42 PM, Marco Bambini <[email protected]> wrote:
> with a bit of work you can use the authorize api in order to know when an > access to a non existing table is performed. > https://sqlite.org/c3ref/set_authorizer.html Interesting work-around, if that works. I.e. whether name resolution to table/column happens before or after the authorizer is called. But it brings up the more general question of knowing which APIs are safe to call inside other APIs, notably when doing schema changes for example. In this case for example, we'd typically be inside a prepare statement, and is it OK to change the schema, potentially affecting that very statement we are currently parsing/resolving/compiling? I.e. API re-entrance but outside the context of multi-threading I guess. --DD _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
