Home | History | Annotate | Download | only in dist

Lines Matching refs:sqlite3_prepare

2584 ** [sqlite3_prepare|prepared] and when it is [sqlite3_step|stepped].
3382 ** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()],
3426 ** An authorizer is used when [sqlite3_prepare | preparing]
3434 ** user-entered SQL is being [sqlite3_prepare | prepared] that
3458 ** [sqlite3_prepare()] or its variants. Authorization is not
3677 ** [sqlite3_step()] and [sqlite3_prepare()] and similar for
3703 ** bytecode engine. It still might be invoked during [sqlite3_prepare()]
3707 ** invoked directly from [sqlite3_prepare()] while analyzing and generating
4499 ** [sqlite3_prepare()] interface is legacy and should be avoided.
4514 ** as either UTF-8 or UTF-16. The sqlite3_prepare(), sqlite3_prepare_v2(),
4545 ** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK];
4550 ** The older interfaces (sqlite3_prepare() and sqlite3_prepare16())
4593 SQLITE_API int sqlite3_prepare(
4762 ** reprepared because it was created using [sqlite3_prepare()] instead of
5235 ** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function
5242 ** interfaces [sqlite3_prepare()] and [sqlite3_prepare16()]. The use of the
5306 ** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces,