Home | History | Annotate | Download | only in dist

Lines Matching defs:SQLITE_CONSTRAINT

790 SQLITE_CONSTRAINT  19   /* Abort due to constraint violation */
884 #define SQLITE_CONSTRAINT_CHECK        (SQLITE_CONSTRAINT | (1<<8))
885 #define SQLITE_CONSTRAINT_COMMITHOOK   (SQLITE_CONSTRAINT | (2<<8))
886 #define SQLITE_CONSTRAINT_FOREIGNKEY   (SQLITE_CONSTRAINT | (3<<8))
887 #define SQLITE_CONSTRAINT_FUNCTION     (SQLITE_CONSTRAINT | (4<<8))
888 #define SQLITE_CONSTRAINT_NOTNULL      (SQLITE_CONSTRAINT | (5<<8))
889 #define SQLITE_CONSTRAINT_PRIMARYKEY   (SQLITE_CONSTRAINT | (6<<8))
890 #define SQLITE_CONSTRAINT_TRIGGER      (SQLITE_CONSTRAINT | (7<<8))
891 #define SQLITE_CONSTRAINT_UNIQUE       (SQLITE_CONSTRAINT | (8<<8))
892 #define SQLITE_CONSTRAINT_VTAB         (SQLITE_CONSTRAINT | (9<<8))
893 #define SQLITE_CONSTRAINT_ROWID        (SQLITE_CONSTRAINT |(10<<8))
894 #define SQLITE_CONSTRAINT_PINNED       (SQLITE_CONSTRAINT |(11<<8))
895 #define SQLITE_CONSTRAINT_DATATYPE     (SQLITE_CONSTRAINT |(12<<8))
8131 ** implementation returns SQLITE_CONSTRAINT, then there is no need to rollback
8133 ** SQLITE_CONSTRAINT, the database contents must be exactly as they were
8135 ** set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by
10540 ** a call to the [xUpdate] method returns [SQLITE_CONSTRAINT], then the entire
10546 ** that if [xUpdate] returns [SQLITE_CONSTRAINT], it will do so before
10552 ** [SQLITE_CONSTRAINT], SQLite handles this as if the ON CONFLICT mode
10561 ** SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT
13014 **   If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT
13059 **   SQLITE_CONSTRAINT, the conflict-handler function is invoked with
75643 ** SQLITE_CONSTRAINT error.  We cannot allow two or more BtShared
75754               return SQLITE_CONSTRAINT;
88472 **   *  OP_Halt with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
88473 **   *  OP_HaltIfNull with P1=SQLITE_CONSTRAINT and P2=OE_Abort.
91180     ** error code is SQLITE_OK or SQLITE_CONSTRAINT, then promote the
91186         if( p->rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT ){
97805     assert( rc==SQLITE_OK || (p->rc&0xff)==SQLITE_CONSTRAINT );
98167 ** Halt with an SQLITE_CONSTRAINT error if there are any unresolved
105196     if( (rc&0xff)==SQLITE_CONSTRAINT && pOp->p4.pVtab->bConstraint ){
109541 ** then return an SQLITE_CONSTRAINT error.
109548   int rc = SQLITE_CONSTRAINT;
123174 ** SQLITE_CONSTRAINT.
123262       SQLITE_CONSTRAINT, zDb, pTab->zName, (int)pCol->n, pCol->z
123371       SQLITE_CONSTRAINT, zDb, pTab->zName, nExpr, pExpr
125615   if( rc==SQLITE_CONSTRAINT ){
131756 ** Code an OP_Halt that causes the vdbe to return an SQLITE_CONSTRAINT
131771   assert( (errCode&0xff)==SQLITE_CONSTRAINT || pParse->nested );
140524 **                                return code of SQLITE_CONSTRAINT.
140529 **                                with SQLITE_CONSTRAINT.
140532 **                                return code of SQLITE_CONSTRAINT.  The
147459     if( pConstraint->usable==0 ) return SQLITE_CONSTRAINT;
170235 ** appropriate error code is returned.  A return of SQLITE_CONSTRAINT from
170236 ** xBestIndex is not considered an error.  SQLITE_CONSTRAINT indicates that
170256   if( rc!=SQLITE_OK && rc!=SQLITE_CONSTRAINT ){
172981     if( rc==SQLITE_CONSTRAINT ){
172982       /* If the xBestIndex method returns SQLITE_CONSTRAINT, that means
188704       case SQLITE_CONSTRAINT:         zName = "SQLITE_CONSTRAINT";        break;
188771     /* SQLITE_CONSTRAINT  */ "constraint failed",
204971       return SQLITE_CONSTRAINT;
209711     rc = SQLITE_CONSTRAINT;
209733   ** detect the conflict and return SQLITE_CONSTRAINT before beginning to
209787       if( rc==SQLITE_CONSTRAINT && p->zContentTbl==0 ){
217848     return SQLITE_CONSTRAINT;
221145 ** SQLITE_CONSTRAINT.
221152 ** If an OOM occurs, SQLITE_NOMEM is returned instead of SQLITE_CONSTRAINT.
221184   return (rc==SQLITE_OK ? SQLITE_CONSTRAINT : rc);
221215   ** SQLITE_CONSTRAINT for two reasons:
221222   ** case, SQLITE_CONSTRAINT must be returned regardless of the
225343 **  pass unnoticed, or result in SQLITE_CONSTRAINT errors (due to UNIQUE
230145 ** If the error code currently stored in the RBU handle is SQLITE_CONSTRAINT,
230150   if( p->rc==SQLITE_CONSTRAINT && p->zErrmsg ){
231595       return SQLITE_CONSTRAINT;
232410       return SQLITE_CONSTRAINT;
233140         return SQLITE_CONSTRAINT;
233145       return SQLITE_CONSTRAINT;
238366     }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
238406     }else if( (rc&0xff)==SQLITE_CONSTRAINT ){
238421         rc = SQLITE_CONSTRAINT;
238434     if( (rc&0xff)==SQLITE_CONSTRAINT ){
238745         rc = SQLITE_CONSTRAINT;
259369 ** then return an SQLITE_CONSTRAINT error.
259376   int rc = SQLITE_CONSTRAINT;
260206 ** SQLITE_CONSTRAINT is returned.
260283         ** unusable plan. Return SQLITE_CONSTRAINT. */
260285         return SQLITE_CONSTRAINT;