Lines Matching full:authorizer
2531 ** ^This routine registers an authorizer callback with a particular
2533 ** ^The authorizer callback is invoked as SQL statements are being compiled
2537 ** to perform various actions, the authorizer callback is invoked to
2538 ** see if those actions are allowed. ^The authorizer callback should
2542 ** rejected with an error. ^If the authorizer callback returns
2545 ** the authorizer will fail with an error message.
2550 ** authorizer will fail with an error message explaining that
2553 ** ^The first parameter to the authorizer callback is a copy of the third
2571 ** An authorizer is used when [sqlite3_prepare | preparing]
2578 ** database. An authorizer could then be put in place while the
2585 ** in addition to using an authorizer.
2587 ** ^(Only a single authorizer can be in place on a database connection
2589 ** previous call.)^ ^Disable the authorizer by installing a NULL callback.
2590 ** The authorizer is disabled by default.
2592 ** The authorizer callback must not do anything that will modify
2593 ** the database connection that invoked the authorizer callback.
2600 ** correct authorizer callback remains in place during the [sqlite3_step()].
2602 ** ^Note that the authorizer callback is invoked only during
2615 ** CAPI3REF: Authorizer Return Codes
2617 ** The [sqlite3_set_authorizer | authorizer callback function] must
2620 ** [sqlite3_set_authorizer | authorizer documentation] for additional
2630 ** CAPI3REF: Authorizer Action Codes
2636 ** the authorizer callback may be passed.
2642 ** authorizer callback is the name of the database ("main", "temp",
2643 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback
