Lines Matching full:authorizer
2745 ** ^This routine registers an authorizer callback with a particular
2747 ** ^The authorizer callback is invoked as SQL statements are being compiled
2751 ** to perform various actions, the authorizer callback is invoked to
2752 ** see if those actions are allowed. ^The authorizer callback should
2756 ** rejected with an error. ^If the authorizer callback returns
2759 ** the authorizer will fail with an error message.
2764 ** authorizer will fail with an error message explaining that
2767 ** ^The first parameter to the authorizer callback is a copy of the third
2785 ** An authorizer is used when [sqlite3_prepare | preparing]
2792 ** database. An authorizer could then be put in place while the
2799 ** in addition to using an authorizer.
2801 ** ^(Only a single authorizer can be in place on a database connection
2803 ** previous call.)^ ^Disable the authorizer by installing a NULL callback.
2804 ** The authorizer is disabled by default.
2806 ** The authorizer callback must not do anything that will modify
2807 ** the database connection that invoked the authorizer callback.
2814 ** correct authorizer callback remains in place during the [sqlite3_step()].
2816 ** ^Note that the authorizer callback is invoked only during
2829 ** CAPI3REF: Authorizer Return Codes
2831 ** The [sqlite3_set_authorizer | authorizer callback function] must
2834 ** [sqlite3_set_authorizer | authorizer documentation] for additional
2844 ** CAPI3REF: Authorizer Action Codes
2850 ** the authorizer callback may be passed.
2856 ** authorizer callback is the name of the database ("main", "temp",
2857 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback
70991 ** collating sequences are registered or if an authorizer function is
92610 sqlite3ErrorMsg(pParse, "authorizer malfunction");
