Lines Matching refs:sqlite3_prepare

3150 ** by [sqlite3_prepare()] or its variants [sqlite3_prepare_v2()],
3194 ** An authorizer is used when [sqlite3_prepare | preparing]
3202 ** user-entered SQL is being [sqlite3_prepare | prepared] that
3226 ** [sqlite3_prepare()] or its variants.  Authorization is not
3445 ** [sqlite3_step()] and [sqlite3_prepare()] and similar for
3471 ** bytecode engine.  It still might be invoked during [sqlite3_prepare()]
3475 ** invoked directly from [sqlite3_prepare()] while analyzing and generating
4205 ** [sqlite3_prepare()] interface is legacy and should be avoided.
4219 ** as either UTF-8 or UTF-16.  The sqlite3_prepare(), sqlite3_prepare_v2(),
4246 ** ^On success, the sqlite3_prepare() family of routines return [SQLITE_OK];
4251 ** The older interfaces (sqlite3_prepare() and sqlite3_prepare16())
4294 SQLITE_API int sqlite3_prepare(
4463 ** reprepared because it was created using [sqlite3_prepare()] instead of
4929 ** interfaces [sqlite3_prepare()] or [sqlite3_prepare16()], this function
4936 ** interfaces [sqlite3_prepare()] and [sqlite3_prepare16()].  The use of the
5000 ** of the legacy [sqlite3_prepare()] and [sqlite3_prepare16()] interfaces,