Searched refs:SQLITE_MISUSE (Results 1 – 5 of 5) sorted by relevance
83 case SQLITE_MISUSE: in _pysqlite_seterror()
466 #define SQLITE_MISUSE 21 /* Library used incorrectly */ macro
776 #define SQLITE_MISUSE 21 /* Library used incorrectly */ macro26865 sqlite3_log(SQLITE_MISUSE,33505 sqlite3_log(SQLITE_MISUSE,84752 sqlite3_log(SQLITE_MISUSE, "API called with finalized prepared statement");84760 sqlite3_log(SQLITE_MISUSE, "API called with NULL prepared statement");85462 || (rc&0xff)==SQLITE_BUSY || rc==SQLITE_MISUSE86076 sqlite3Error(p->db, SQLITE_MISUSE);86078 sqlite3_log(SQLITE_MISUSE,145910 sqlite3Error(db, SQLITE_MISUSE);168143 rc = SQLITE_MISUSE;[all …]
11142 if( p->bRun ) return SQLITE_MISUSE; in sqlite3_expert_sql()22218 if( sqlite3_config(-1)==SQLITE_MISUSE ){ in verify_uninitialized()
91535 +** processing, then these routines return [SQLITE_MISUSE])^ or perhaps98372 - ** be called automatically instead of throwing the SQLITE_MISUSE error.98374 - ** since any application that receives an SQLITE_MISUSE is broken by98378 - ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE98381 - ** legacy behavior of returning SQLITE_MISUSE for cases where the98483 + ** be called automatically instead of throwing the SQLITE_MISUSE error.98485 + ** since any application that receives an SQLITE_MISUSE is broken by98489 + ** for version 3.6.23 or earlier do in fact depend on SQLITE_MISUSE98492 + ** legacy behavior of returning SQLITE_MISUSE for cases where the98567 + if( pVal==0 ) return SQLITE_MISUSE;[all …]