contrib/sqlite3/sqlite3.c

695 #define SQLITE_MISUSE      21   /* Library used incorrectly */
1675 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
3520 ** If an interface fails with SQLITE_MISUSE, that means the interface
4008 ** then the call will return [SQLITE_MISUSE].  If any sqlite3_bind_()
4262 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
4292 ** [SQLITE_MISUSE] means that the this routine was called inappropriately.
4303 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4306 ** than returning [SQLITE_MISUSE].  This is not considered a compatibility
4307 ** break because any application that ever receives an SQLITE_MISUSE error
4313 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
4625 ** will result in [SQLITE_MISUSE] being returned.
5683 ** and will always return SQLITE_MISUSE. On those systems,
6385 ** code is SQLITE_MISUSE, *ppBlob is set to NULL.)^ ^This means that, provided
6405 ** ^Unless it returns SQLITE_MISUSE, this function sets the
6546 ** ^Unless SQLITE_MISUSE is returned, this function sets the
8119 ** ^Unless it returns SQLITE_MISUSE,
9185 ** a conflict-handler callback by [sqlite3changeset_apply()], SQLITE_MISUSE
9211 ** is not the case, this function returns [SQLITE_MISUSE].
9259 ** entry, SQLITE_MISUSE is returned and the output variables zeroed. Otherwise,
9278 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL.
9308 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL.
9338 ** is called on any other iterator, [SQLITE_MISUSE] is returned and *ppValue
9367 ** In all other cases this function returns SQLITE_MISUSE.
9384 ** [sqlite3changeset_apply()], [SQLITE_MISUSE] is immediately returned and the
9673 ** the call to sqlite3changeset_apply() returns SQLITE_MISUSE. Different
9849 **   call to sqlite3changeset_apply() returns SQLITE_MISUSE.
14085 #define SQLITE_MAGIC_ERROR    0xb5357930  /* An SQLITE_MISUSE error occurred */
28427   sqlite3_log(SQLITE_MISUSE,
28440 ** SQLITE_MISUSE immediately.
36622           rc = SQLITE_ERROR /*SQLITE_PROTOCOL? SQLITE_MISUSE?*/;
74985     sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
74993     sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
75473     ** be called automatically instead of throwing the SQLITE_MISUSE error.
75475     ** since any application that receives an SQLITE_MISUSE is broken by
75479     ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE
75482     ** legacy behavior of returning SQLITE_MISUSE for cases where the
75576        || (rc&0xff)==SQLITE_BUSY || rc==SQLITE_MISUSE
76178     sqlite3Error(p->db, SQLITE_MISUSE);
76180     sqlite3_log(SQLITE_MISUSE,
122448     sqlite3Error(db, SQLITE_MISUSE);
136854   /* sqlite3_config() shall return SQLITE_MISUSE if it is invoked while
137844       case SQLITE_MISUSE:             zName = "SQLITE_MISUSE";            break;
137896     /* SQLITE_MISUSE      */ "library routine called out of sequence",
138581     return SQLITE_MISUSE;
139764 ** SQLITE_MISUSE, SQLITE_CANTOPEN, SQLITE_NOMEM and possibly other error
139784   return reportError(SQLITE_MISUSE, lineno, "misuse");
173297 ** Otherwise, SQLITE_MISUSE is returned.
173313     return SQLITE_MISUSE;
173325 ** Otherwise, SQLITE_MISUSE is returned.
173341     return SQLITE_MISUSE;
173361 ** conflict-handler function. Otherwise, SQLITE_MISUSE is returned.
173375     return SQLITE_MISUSE;
173390 ** In all other cases this function returns SQLITE_MISUSE.
173397     return SQLITE_MISUSE;
173994 ** SQLITE_MISUSE. If the conflict handler returns SQLITE_CHANGESET_OMIT,
174041       if( res==SQLITE_CHANGESET_REPLACE ) rc = SQLITE_MISUSE;
174060         rc = SQLITE_MISUSE;