contrib/sqlite3/sqlite3.c

2888 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the
2892 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY]
2910 ** and the callback returns [SQLITE_IGNORE] then the
2913 ** been read if [SQLITE_OK] had been returned.  The [SQLITE_IGNORE]
2917 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the
2972 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode]
2976 #define SQLITE_IGNORE 2   /* Don't allow access, but don't generate an error */
8211 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL],
8226 ** Note that the [SQLITE_IGNORE] constant is also used as a potential
8231 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
97183 ** should return either SQLITE_OK, SQLITE_DENY, or SQLITE_IGNORE.  If
97186 ** will return with an error.  SQLITE_IGNORE means that the SQL statement
97223 ** If SQLITE_IGNORE is returned and pExpr is not NULL, then pExpr is changed
97224 ** to an SQL NULL expression. Otherwise, if pExpr is NULL, then SQLITE_IGNORE
97250   }else if( rc!=SQLITE_IGNORE && rc!=SQLITE_OK ){
97261 ** If the auth function returns SQLITE_IGNORE, change the TK_COLUMN
97311   if( SQLITE_IGNORE==sqlite3AuthReadCol(pParse, pTab->zName, zCol, iDb) ){
97318 ** either SQLITE_OK (zero) or SQLITE_IGNORE or SQLITE_DENY.  If SQLITE_DENY
97350   }else if( rc!=SQLITE_OK && rc!=SQLITE_IGNORE ){
102602   assert( rcauth==SQLITE_OK || rcauth==SQLITE_DENY || rcauth==SQLITE_IGNORE );
105997       ** authorization callback returns SQLITE_IGNORE, behave as if any
106003         bIgnore = (rcauth==SQLITE_IGNORE);
120757       }else if( rc==SQLITE_IGNORE ){
122892     SQLITE_ROLLBACK, SQLITE_ABORT, SQLITE_FAIL, SQLITE_IGNORE, SQLITE_REPLACE