Lines Matching defs:SQLITE_IGNORE

2965 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the
2969 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY]
2987 ** and the callback returns [SQLITE_IGNORE] then the
2990 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE]
2994 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the
3049 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode]
3053 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */
8313 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL],
8328 ** Note that the [SQLITE_IGNORE] constant is also used as a potential
8333 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
99250 ** should return either SQLITE_OK, SQLITE_DENY, or SQLITE_IGNORE. If
99253 ** will return with an error. SQLITE_IGNORE means that the SQL statement
99290 ** If SQLITE_IGNORE is returned and pExpr is not NULL, then pExpr is changed
99291 ** to an SQL NULL expression. Otherwise, if pExpr is NULL, then SQLITE_IGNORE
99317 }else if( rc!=SQLITE_IGNORE && rc!=SQLITE_OK ){
99328 ** If the auth function returns SQLITE_IGNORE, change the TK_COLUMN
99378 if( SQLITE_IGNORE==sqlite3AuthReadCol(pParse, pTab->zName, zCol, iDb) ){
99385 ** either SQLITE_OK (zero) or SQLITE_IGNORE or SQLITE_DENY. If SQLITE_DENY
99417 }else if( rc!=SQLITE_OK && rc!=SQLITE_IGNORE ){
104684 assert( rcauth==SQLITE_OK || rcauth==SQLITE_DENY || rcauth==SQLITE_IGNORE );
108103 ** authorization callback returns SQLITE_IGNORE, behave as if any
108109 bIgnore = (rcauth==SQLITE_IGNORE);
123547 }else if( rc==SQLITE_IGNORE ){
125720 SQLITE_ROLLBACK, SQLITE_ABORT, SQLITE_FAIL, SQLITE_IGNORE, SQLITE_REPLACE