Lines Matching refs:SQLITE_CONSTRAINT
1466 #define SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */
1545 #define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT | (1<<8))
1546 #define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT | (2<<8))
1547 #define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT | (3<<8))
1548 #define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT | (4<<8))
1549 #define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT | (5<<8))
1550 #define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT | (6<<8))
1551 #define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT | (7<<8))
1552 #define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT | (8<<8))
1553 #define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT | (9<<8))
1554 #define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT |(10<<8))
7245 ** implementation returns SQLITE_CONSTRAINT, then there is no need to rollback
7247 ** SQLITE_CONSTRAINT, the database contents must be exactly as they were
7249 ** set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by
9301 ** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire
9307 ** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before
9313 ** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode
9322 ** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT
10943 ** If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT
10988 ** SQLITE_CONSTRAINT, the conflict-handler function is invoked with
62657 ** SQLITE_CONSTRAINT error. We cannot allow two or more BtShared
62764 return SQLITE_CONSTRAINT;
73449 ** * OP_Halt with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
73450 ** * OP_HaltIfNull with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
73479 && ((pOp->p1&0xff)==SQLITE_CONSTRAINT && pOp->p2==OE_Abort))
75718 ** error code is SQLITE_OK or SQLITE_CONSTRAINT, then promote the
75724 if( p->rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT ){
80978 assert( rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT );
86887 if( (rc&0xff)==SQLITE_CONSTRAINT && pOp->p4.pVtab->bConstraint ){
100907 if( rc==SQLITE_CONSTRAINT ){
105756 ** Code an OP_Halt that causes the vdbe to return an SQLITE_CONSTRAINT
105769 assert( (errCode&0xff)==SQLITE_CONSTRAINT );
112029 ** return code of SQLITE_CONSTRAINT.
112034 ** with SQLITE_CONSTRAINT.
112037 ** return code of SQLITE_CONSTRAINT. The
144728 case SQLITE_CONSTRAINT: zName = "SQLITE_CONSTRAINT"; break;
144794 /* SQLITE_CONSTRAINT */ "constraint failed",
159866 return SQLITE_CONSTRAINT;
164456 rc = SQLITE_CONSTRAINT;
164478 ** detect the conflict and return SQLITE_CONSTRAINT before beginning to
164533 if( rc==SQLITE_CONSTRAINT && p->zContentTbl==0 ){
170024 ** SQLITE_CONSTRAINT.
170031 ** If an OOM occurs, SQLITE_NOMEM is returned instead of SQLITE_CONSTRAINT.
170063 return (rc==SQLITE_OK ? SQLITE_CONSTRAINT : rc);
170088 ** SQLITE_CONSTRAINT for two reasons:
170095 ** case, SQLITE_CONSTRAINT must be returned regardless of the
172184 ** pass unnoticed, or result in SQLITE_CONSTRAINT errors (due to UNIQUE
176470 ** If the error code currently stored in the RBU handle is SQLITE_CONSTRAINT,
176475 if( p->rc==SQLITE_CONSTRAINT && p->zErrmsg ){
182656 }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
182697 }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
182712 rc = SQLITE_CONSTRAINT;
182725 if( (rc&0xff)==SQLITE_CONSTRAINT ){
183005 rc = SQLITE_CONSTRAINT;
