Lines Matching refs:SQLITE_CONSTRAINT

1504 #define SQLITE_CONSTRAINT  19   /* Abort due to constraint violation */
1592 #define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT | (1<<8))
1593 #define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT | (2<<8))
1594 #define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT | (3<<8))
1595 #define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT | (4<<8))
1596 #define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT | (5<<8))
1597 #define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT | (6<<8))
1598 #define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT | (7<<8))
1599 #define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT | (8<<8))
1600 #define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT | (9<<8))
1601 #define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT |(10<<8))
1602 #define SQLITE_CONSTRAINT_PINNED (SQLITE_CONSTRAINT |(11<<8))
7958 ** implementation returns SQLITE_CONSTRAINT, then there is no need to rollback
7960 ** SQLITE_CONSTRAINT, the database contents must be exactly as they were
7962 ** set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by
10260 ** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire
10266 ** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before
10272 ** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode
10281 ** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT
12140 ** If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT
12185 ** SQLITE_CONSTRAINT, the conflict-handler function is invoked with
67313 ** SQLITE_CONSTRAINT error. We cannot allow two or more BtShared
67424 return SQLITE_CONSTRAINT;
79052 ** * OP_Halt with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
79053 ** * OP_HaltIfNull with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
81532 ** error code is SQLITE_OK or SQLITE_CONSTRAINT, then promote the
81538 if( p->rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT ){
87085 assert( rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT );
93764 if( (rc&0xff)==SQLITE_CONSTRAINT && pOp->p4.pVtab->bConstraint ){
97866 ** then return an SQLITE_CONSTRAINT error.
97873 int rc = SQLITE_CONSTRAINT;
110885 if( rc==SQLITE_CONSTRAINT ){
116543 ** Code an OP_Halt that causes the vdbe to return an SQLITE_CONSTRAINT
116558 assert( (errCode&0xff)==SQLITE_CONSTRAINT || pParse->nested );
123706 ** return code of SQLITE_CONSTRAINT.
123711 ** with SQLITE_CONSTRAINT.
123714 ** return code of SQLITE_CONSTRAINT. The
149389 ** appropriate error code is returned. A return of SQLITE_CONSTRAINT from
149390 ** xBestIndex is not considered an error. SQLITE_CONSTRAINT indicates that
149406 if( rc!=SQLITE_OK && rc!=SQLITE_CONSTRAINT ){
151562 if( rc==SQLITE_CONSTRAINT ){
151563 /* If the xBestIndex method returns SQLITE_CONSTRAINT, that means
165584 case SQLITE_CONSTRAINT: zName = "SQLITE_CONSTRAINT"; break;
165650 /* SQLITE_CONSTRAINT */ "constraint failed",
181194 return SQLITE_CONSTRAINT;
185897 rc = SQLITE_CONSTRAINT;
185919 ** detect the conflict and return SQLITE_CONSTRAINT before beginning to
185973 if( rc==SQLITE_CONSTRAINT && p->zContentTbl==0 ){
190935 return SQLITE_CONSTRAINT;
194334 ** SQLITE_CONSTRAINT.
194341 ** If an OOM occurs, SQLITE_NOMEM is returned instead of SQLITE_CONSTRAINT.
194373 return (rc==SQLITE_OK ? SQLITE_CONSTRAINT : rc);
194404 ** SQLITE_CONSTRAINT for two reasons:
194411 ** case, SQLITE_CONSTRAINT must be returned regardless of the
198446 ** pass unnoticed, or result in SQLITE_CONSTRAINT errors (due to UNIQUE
203144 ** If the error code currently stored in the RBU handle is SQLITE_CONSTRAINT,
203149 if( p->rc==SQLITE_CONSTRAINT && p->zErrmsg ){
204519 return SQLITE_CONSTRAINT;
205278 return SQLITE_CONSTRAINT;
209806 }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
209846 }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
209861 rc = SQLITE_CONSTRAINT;
209874 if( (rc&0xff)==SQLITE_CONSTRAINT ){
210169 rc = SQLITE_CONSTRAINT;