Fix #583 by keeping a single authorizer active for the whole lifetime of a database connection
Fix #583 by keeping a single authorizer active for the whole lifetime of a database connection

SQLite invalidates statements when authorizer changes, which can lead to undesired behaviors. This is why we now call sqlite3_set_authorizer only once. See http://sqlite.1065341.n5.nabble.com/Issue-report-sqlite3-set-authorizer-triggers-error-4-516-SQLITE-ABORT-ROLLBACK-during-statement-itern-td107972.html

groue/GRDB.swift,groue/GRDB.swift,groue/GRDB.swift,groue/GRDB.swift