Lines Matching refs:SQLITE_MISUSE
956 #define SQLITE_MISUSE 21 /* Library used incorrectly */
1707 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
3191 ** If an interface fails with SQLITE_MISUSE, that means the interface
3600 ** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_()
3837 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
3867 ** [SQLITE_MISUSE] means that the this routine was called inappropriately.
3878 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
3881 ** than returning [SQLITE_MISUSE]. This is not considered a compatibility
3882 ** break because any application that ever receives an SQLITE_MISUSE error
3888 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4196 ** will result in [SQLITE_MISUSE] being returned.
9617 #define SQLITE_MAGIC_ERROR 0xb5357930 /* An SQLITE_MISUSE error occurred */
21646 sqlite3_log(SQLITE_MISUSE,
21659 ** SQLITE_MISUSE immediately.
31059 rc = SQLITE_ERROR /*SQLITE_PROTOCOL? SQLITE_MISUSE?*/;
61585 sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
61593 sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
61894 ** be called automatically instead of throwing the SQLITE_MISUSE error.
61896 ** since any application that receives an SQLITE_MISUSE is broken by
61900 ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE
61903 ** legacy behavior of returning SQLITE_MISUSE for cases where the
61993 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
62539 sqlite3Error(p->db, SQLITE_MISUSE, 0);
62541 sqlite3_log(SQLITE_MISUSE,
99947 sqlite3Error(db, SQLITE_MISUSE, 0);
110437 /* sqlite3_config() shall return SQLITE_MISUSE if it is invoked while
111023 /* SQLITE_MISUSE */ "library routine called out of sequence",
111562 return SQLITE_MISUSE;
112621 ** SQLITE_MISUSE, SQLITE_CANTOPEN, SQLITE_IOERR and possibly other error
112639 sqlite3_log(SQLITE_MISUSE,
112642 return SQLITE_MISUSE;