Lines Matching refs:SQLITE_MISUSE
953 #define SQLITE_MISUSE 21 /* Library used incorrectly */
1771 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.
3286 ** If an interface fails with SQLITE_MISUSE, that means the interface
3722 ** then the call will return [SQLITE_MISUSE]. If any sqlite3_bind_()
3959 ** [SQLITE_DONE], [SQLITE_ROW], [SQLITE_ERROR], or [SQLITE_MISUSE].
3989 ** [SQLITE_MISUSE] means that the this routine was called inappropriately.
4000 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4003 ** than returning [SQLITE_MISUSE]. This is not considered a compatibility
4004 ** break because any application that ever receives an SQLITE_MISUSE error
4010 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4324 ** will result in [SQLITE_MISUSE] being returned.
9881 #define SQLITE_MAGIC_ERROR 0xb5357930 /* An SQLITE_MISUSE error occurred */
22082 sqlite3_log(SQLITE_MISUSE,
22095 ** SQLITE_MISUSE immediately.
31612 rc = SQLITE_ERROR /*SQLITE_PROTOCOL? SQLITE_MISUSE?*/;
62788 sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");
62796 sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");
63097 ** be called automatically instead of throwing the SQLITE_MISUSE error.
63099 ** since any application that receives an SQLITE_MISUSE is broken by
63103 ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE
63106 ** legacy behavior of returning SQLITE_MISUSE for cases where the
63196 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
63742 sqlite3Error(p->db, SQLITE_MISUSE, 0);
63744 sqlite3_log(SQLITE_MISUSE,
102134 sqlite3Error(db, SQLITE_MISUSE, 0);
112733 /* sqlite3_config() shall return SQLITE_MISUSE if it is invoked while
113352 /* SQLITE_MISUSE
113899 return SQLITE_MISUSE;
114955 ** SQLITE_MISUSE
114973 sqlite3_log(SQLITE_MISUSE,
114976 return SQLITE_MISUSE;
