Feature request: support for SQLite's authorizer (sqlite3_set_authorizer)

[asaikali]

Summary

Please add support for SQLite's authorizer callback (sqlite3_set_authorizer) to the JDBC driver. As far as I can tell it isn't currently exposed in any form.

Use case

I'd like to enforce per-table access control on a single connection: deny both reads and writes to a set of privileged tables (e.g. a sys_ prefix) while allowing normal access to the rest. The authorizer is the SQLite mechanism designed for this — it gates reads as well as writes, pre-execution, and applies even when tables are accessed indirectly through views, subqueries, or triggers.

Note

This would follow the same precedent as the existing callback hooks already exposed by the driver (busy handler, progress handler, commit/update listeners).

Version: observed against 3.53.2.

[hiSandog]

If this is added, the API shape probably needs to make the callback lifecycle very explicit. sqlite3_set_authorizer is connection-scoped and can be invoked during statement preparation/execution, so a Java wrapper should define whether the authorizer is thread-confined to the connection, how exceptions map to SQLite deny/error codes, and how to clear/reset the callback. A small test using a view or trigger would also prove that indirect table access is covered, which is one of the main reasons to use the SQLite authorizer instead of SQL rewriting.