Lines Matching full:authorizer
2791 ** ^This routine registers an authorizer callback with a particular
2793 ** ^The authorizer callback is invoked as SQL statements are being compiled
2797 ** to perform various actions, the authorizer callback is invoked to
2798 ** see if those actions are allowed. ^The authorizer callback should
2802 ** rejected with an error. ^If the authorizer callback returns
2805 ** the authorizer will fail with an error message.
2810 ** authorizer will fail with an error message explaining that
2813 ** ^The first parameter to the authorizer callback is a copy of the third
2831 ** An authorizer is used when [sqlite3_prepare | preparing]
2838 ** database. An authorizer could then be put in place while the
2845 ** in addition to using an authorizer.
2847 ** ^(Only a single authorizer can be in place on a database connection
2849 ** previous call.)^ ^Disable the authorizer by installing a NULL callback.
2850 ** The authorizer is disabled by default.
2852 ** The authorizer callback must not do anything that will modify
2853 ** the database connection that invoked the authorizer callback.
2860 ** correct authorizer callback remains in place during the [sqlite3_step()].
2862 ** ^Note that the authorizer callback is invoked only during
2875 ** CAPI3REF: Authorizer Return Codes
2877 ** The [sqlite3_set_authorizer | authorizer callback function] must
2880 ** [sqlite3_set_authorizer | authorizer documentation] for additional
2890 ** CAPI3REF: Authorizer Action Codes
2896 ** the authorizer callback may be passed.
2902 ** authorizer callback is the name of the database ("main", "temp",
2903 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback
62772 ** collating sequences are registered or if an authorizer function is
81033 sqlite3ErrorMsg(pParse, "authorizer malfunction");
