Cross Reference: /external/sqlite/dist/sqlite3.c

Lines Matching refs:SQLITE_MISUSE
717 #define SQLITE_MISUSE      21   /* Library used incorrectly */
1756 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
3648 ** If an interface fails with SQLITE_MISUSE, that means the interface
4141 ** then the call will return [SQLITE_MISUSE].  If any sqlite3_bind_()
4399 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
4429 ** [SQLITE_MISUSE] means that the this routine was called inappropriately.
4440 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4444 ** than returning [SQLITE_MISUSE].  This is not considered a compatibility
4445 ** break because any application that ever receives an SQLITE_MISUSE error
4451 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
4763 ** will result in [SQLITE_MISUSE] being returned.
5827 ** and will always return SQLITE_MISUSE. On those systems, 
6532 ** code is SQLITE_MISUSE, *ppBlob is set to NULL.)^ ^This means that, provided
6552 ** ^Unless it returns SQLITE_MISUSE, this function sets the 
6703 ** ^Unless SQLITE_MISUSE is returned, this function sets the 
8277 ** ^Unless it returns SQLITE_MISUSE,
9397 ** a conflict-handler callback by [sqlite3changeset_apply()], SQLITE_MISUSE
9423 ** is not the case, this function returns [SQLITE_MISUSE].
9471 ** entry, SQLITE_MISUSE is returned and the output variables zeroed. Otherwise,
9490 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL.
9520 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL.
9550 ** is called on any other iterator, [SQLITE_MISUSE] is returned and *ppValue
9579 ** In all other cases this function returns SQLITE_MISUSE.
9596 ** [sqlite3changeset_apply()], [SQLITE_MISUSE] is immediately returned and the
9889 ** the call to sqlite3changeset_apply() returns SQLITE_MISUSE. Different 
10071 **   call to sqlite3changeset_apply() returns SQLITE_MISUSE.
14364 #define SQLITE_MAGIC_ERROR    0xb5357930  /* An SQLITE_MISUSE error occurred */
28937   sqlite3_log(SQLITE_MISUSE, 
28950 ** SQLITE_MISUSE immediately.
37321           rc = SQLITE_ERROR /*SQLITE_PROTOCOL? SQLITE_MISUSE?*/;
76307     sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
76315     sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
76796     ** be called automatically instead of throwing the SQLITE_MISUSE error.
76798     ** since any application that receives an SQLITE_MISUSE is broken by
76802     ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE 
76805     ** legacy behavior of returning SQLITE_MISUSE for cases where the 
76899        || (rc&0xff)==SQLITE_BUSY || rc==SQLITE_MISUSE
77516     sqlite3Error(p->db, SQLITE_MISUSE);
77518     sqlite3_log(SQLITE_MISUSE, 
125881     sqlite3Error(db, SQLITE_MISUSE);
140972   /* sqlite3_config() shall return SQLITE_MISUSE if it is invoked while
141983       case SQLITE_MISUSE:             zName = "SQLITE_MISUSE";            break;
142035     /* SQLITE_MISUSE      */ "library routine called out of sequence",
142722     return SQLITE_MISUSE;
143926 ** SQLITE_MISUSE, SQLITE_CANTOPEN, SQLITE_NOMEM and possibly other error
143946   return reportError(SQLITE_MISUSE, lineno, "misuse");
173077 ** error code, which is set to SQLITE_MISUSE.
173084     pRet->rc = SQLITE_MISUSE;
177862 ** Otherwise, SQLITE_MISUSE is returned.
177878     return SQLITE_MISUSE;
177890 ** Otherwise, SQLITE_MISUSE is returned.
177906     return SQLITE_MISUSE;
177926 ** conflict-handler function. Otherwise, SQLITE_MISUSE is returned.
177940     return SQLITE_MISUSE;
177955 ** In all other cases this function returns SQLITE_MISUSE.
177962     return SQLITE_MISUSE;
178565 ** SQLITE_MISUSE. If the conflict handler returns SQLITE_CHANGESET_OMIT,
178612       if( res==SQLITE_CHANGESET_REPLACE ) rc = SQLITE_MISUSE;
178631         rc = SQLITE_MISUSE;