Searched refs:SQLITE_IGNORE (Results 1 - 5 of 5) sorted by relevance
/freebsd-10-stable/crypto/heimdal/lib/sqlite/ |
H A D | sqlite3.h | 2175 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 2179 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 2197 ** and the callback returns [SQLITE_IGNORE] then the 2200 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 2204 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 2259 ** Note that SQLITE_IGNORE is also used as a [SQLITE_ROLLBACK | return code] 2263 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ macro 6663 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 6677 ** Note that the [SQLITE_IGNORE] constant is also used as a potential 6682 /* #define SQLITE_IGNORE [all...] |
H A D | sqlite3.c | 2728 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 2732 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 2750 ** and the callback returns [SQLITE_IGNORE] then the 2753 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 2757 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 2812 ** Note that SQLITE_IGNORE is also used as a [SQLITE_ROLLBACK | return code] 2816 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ macro 7216 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 7230 ** Note that the [SQLITE_IGNORE] constant is also used as a potential 7235 /* #define SQLITE_IGNORE [all...] |
/freebsd-10-stable/contrib/sqlite3/ |
H A D | sqlite3.h | 2628 ** return [SQLITE_OK] to allow the action, [SQLITE_IGNORE] to disallow the 2632 ** any value other than [SQLITE_IGNORE], [SQLITE_OK], or [SQLITE_DENY] 2650 ** and the callback returns [SQLITE_IGNORE] then the 2653 ** been read if [SQLITE_OK] had been returned. The [SQLITE_IGNORE] 2657 ** [SQLITE_IGNORE] then the [DELETE] operation proceeds but the 2712 ** Note that SQLITE_IGNORE is also used as a [conflict resolution mode] 2716 #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ macro 7951 ** value returned is one of [SQLITE_ROLLBACK], [SQLITE_IGNORE], [SQLITE_FAIL], 7966 ** Note that the [SQLITE_IGNORE] constant is also used as a potential 7971 /* #define SQLITE_IGNORE [all...] |
H A D | 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 */ macro 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 [all...] |
/freebsd-10-stable/contrib/sqlite3/tea/generic/ |
H A D | tclsqlite3.c | 1096 }else if( strcmp(zReply,"SQLITE_IGNORE")==0 ){ 1097 rc = SQLITE_IGNORE; 1881 ** SQLITE_IGNORE, or SQLITE_DENY. Any other return value is an error.
|
Completed in 864 milliseconds