Lines Matching refs:SQLITE_MISUSE
993 #define SQLITE_MISUSE 21 /* Library used incorrectly */
1868 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
3448 ** If an interface fails with SQLITE_MISUSE, that means the interface
3892 ** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_()
4129 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
4159 ** [SQLITE_MISUSE] means that the this routine was called inappropriately.
4170 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4173 ** than returning [SQLITE_MISUSE]. This is not considered a compatibility
4174 ** break because any application that ever receives an SQLITE_MISUSE error
4180 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4494 ** will result in [SQLITE_MISUSE] being returned.
10215 #define SQLITE_MAGIC_ERROR 0xb5357930 /* An SQLITE_MISUSE error occurred */
22290 sqlite3_log(SQLITE_MISUSE,
22303 ** SQLITE_MISUSE immediately.
30216 rc = SQLITE_ERROR /*SQLITE_PROTOCOL? SQLITE_MISUSE?*/;
63241 sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
63249 sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
63544 ** be called automatically instead of throwing the SQLITE_MISUSE error.
63546 ** since any application that receives an SQLITE_MISUSE is broken by
63550 ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE
63553 ** legacy behavior of returning SQLITE_MISUSE for cases where the
63643 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
64183 sqlite3Error(p->db, SQLITE_MISUSE, 0);
64185 sqlite3_log(SQLITE_MISUSE,
103974 sqlite3Error(db, SQLITE_MISUSE, 0);
115106 /* sqlite3_config() shall return SQLITE_MISUSE if it is invoked while
115909 case SQLITE_MISUSE: zName = "SQLITE_MISUSE"; break;
115960 /* SQLITE_MISUSE */ "library routine called out of sequence",
116508 return SQLITE_MISUSE;
117584 ** SQLITE_MISUSE, SQLITE_CANTOPEN, SQLITE_IOERR and possibly other error
117602 sqlite3_log(SQLITE_MISUSE,
117605 return SQLITE_MISUSE;