Lines Matching full:calling
260 ** ^Calling sqlite3_close() with a NULL pointer argument is a
792 ** The xSleep() method causes the calling thread to sleep for at
1382 ** ^Calling [sqlite3_exec()] or [sqlite3_step()] recursively does
1562 ** previously set handler.)^ ^Note that calling [sqlite3_busy_timeout()]
1584 ** ^Calling this routine with an argument less than or equal to zero
1589 ** was defined (using [sqlite3_busy_handler()]) prior to calling
1651 ** [sqlite3_malloc()] happens within sqlite3_get_table(), the calling
1784 ** ^Calling sqlite3_free() with a pointer previously returned
1799 ** is a NULL pointer then its behavior is identical to calling
1802 ** negative then the behavior is exactly the same as calling
2241 ** <li> Run the SQL by calling [sqlite3_step()] one or more times.
2384 ** The calling procedure is responsible for deleting the compiled
2406 ** now a fatal error. Calling [sqlite3_prepare_v2()] again will not make the
2828 ** machine without first calling [sqlite3_reset()] to reset the virtual
2838 ** the VM. More information may be found by calling [sqlite3_errmsg()].
2841 ** can be obtained by calling [sqlite3_reset()] on the
3476 ** they return. Hence, the calling function can deallocate or
3700 ** ^SQLite implements this interface by calling the xSleep()
4050 ** obtained from [sqlite3_malloc()]. The calling function
4051 ** should free this memory by calling [sqlite3_free()].
4054 ** [sqlite3_enable_load_extension()] prior to calling this API,
4096 ** ^Duplicate extensions are detected so calling this routine
4490 ** ^Calling this routine with a null pointer (such as would be returned
4640 ** before calling sqlite3_initialize() or any other public sqlite3_
4714 ** calling thread or is not currently allocated. SQLite will
4821 ** is held or not held, respectively, by the calling thread.
5297 ** calling the xDestroy() method, SQLite considers the [sqlite3_pcache*]
5659 ** nothing to prevent an application from calling sqlite3_log(), doing so
