Controls whether user SQL may create connection-local state.
"strict" rejects SQL whose effect depends on which physical connection
the pool happens to lease: PRAGMA, ATTACH/DETACH, transaction and
savepoint control, temp-schema mutation, extension loading, and the
connection-observing functions last_insert_rowid(), changes(), and
total_changes(). Ordinary main-schema reads and writes are allowed.
"none" installs no persistent authorizer. SQL may then create state that
differs across connections, so a later call can observe a different value.
Strict mode is a pool-consistency policy. It is not a read-only mode, it
imposes no SQLite resource limits, and it is not a sandbox for untrusted SQL.
Both modes still require exactly one executable statement per operation.
Controls whether user SQL may create connection-local state.
"strict"rejects SQL whose effect depends on which physical connection the pool happens to lease:PRAGMA,ATTACH/DETACH, transaction and savepoint control, temp-schema mutation, extension loading, and the connection-observing functionslast_insert_rowid(),changes(), andtotal_changes(). Ordinary main-schema reads and writes are allowed."none"installs no persistent authorizer. SQL may then create state that differs across connections, so a later call can observe a different value.Strict mode is a pool-consistency policy. It is not a read-only mode, it imposes no SQLite resource limits, and it is not a sandbox for untrusted SQL.
Both modes still require exactly one executable statement per operation.