Lines Matching defs:SQLITE_IGNORE

3469 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the
3473 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY]
3493 ** and the callback returns [SQLITE_IGNORE] then the
3496 ** been read if [SQLITE_OK] had been returned.  The [SQLITE_IGNORE]
3504 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the
3559 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode]
3563 #define SQLITE_IGNORE 2   /* Don't allow access, but don't generate an error */
10158 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL],
10491 ** Note that the [SQLITE_IGNORE] constant is also used as a potential
10496 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
121156 ** should return either SQLITE_OK, SQLITE_DENY, or SQLITE_IGNORE.  If
121159 ** will return with an error.  SQLITE_IGNORE means that the SQL statement
121196 ** If SQLITE_IGNORE is returned and pExpr is not NULL, then pExpr is changed
121197 ** to an SQL NULL expression. Otherwise, if pExpr is NULL, then SQLITE_IGNORE
121221   }else if( rc!=SQLITE_IGNORE && rc!=SQLITE_OK ){
121232 ** If the auth function returns SQLITE_IGNORE, change the TK_COLUMN
121282   if( SQLITE_IGNORE==sqlite3AuthReadCol(pParse, pTab->zName, zCol, iDb) ){
121289 ** either SQLITE_OK (zero) or SQLITE_IGNORE or SQLITE_DENY.  If SQLITE_DENY
121330   }else if( rc!=SQLITE_OK && rc!=SQLITE_IGNORE ){
128010   assert( rcauth==SQLITE_OK || rcauth==SQLITE_DENY || rcauth==SQLITE_IGNORE );
128082   ** the callback returns SQLITE_IGNORE then the DELETE operation proceeds but
132385       ** authorization callback returns SQLITE_IGNORE, behave as if any
132391         bIgnore = (rcauth==SQLITE_IGNORE);
153792       }else if( rc==SQLITE_IGNORE ){
156704     SQLITE_ROLLBACK, SQLITE_ABORT, SQLITE_FAIL, SQLITE_IGNORE, SQLITE_REPLACE