Lines Matching refs:flag
244 ** of the [SQLITE_THREADSAFE] flag. If SQLite is compiled with
585 ** Note in particular that passing the SQLITE_OPEN_EXCLUSIVE flag into
642 ** flag indicates that a file cannot be deleted when open. The
643 ** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on
692 ** When the SQLITE_SYNC_DATAONLY flag is used, it means that the
694 ** information need not be flushed. If the lower four bits of the flag
750 ** flag may be ORed in to indicate that only the data of the file
1381 ** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be
1386 ** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction
1387 ** with the [SQLITE_OPEN_CREATE] flag, which are both directly
1389 ** API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the
1410 ** flag is never actually used and is not implemented in the built-in
1535 ** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as
1993 ** of whether or not the [SQLITE_OPEN_URI] flag is set when the database
1995 ** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the
2304 ** option is used to set or clear (the default) a flag that governs this
2314 ** <dd> Set the SQLITE_DBCONFIG_RESET_DATABASE flag and then run
2335 ** "defensive" flag for a database connection. When the defensive
2336 ** flag is enabled, language features that allow ordinary SQL to
2350 ** "writable_schema" flag. This has the same effect and is logically equivalent
2410 ** the legacy file format flag. When activated, this flag causes all newly
3410 ** three flag combinations:)^
3433 ** <dd>The filename can be interpreted as a URI if this flag is set.</dd>)^
3472 ** the extended result code mode, this flag also causes [sqlite3_open_v2()]
3486 ** upon it. Note in particular that the SQLITE_OPEN_EXCLUSIVE flag is a no-op
3489 ** flag is intended for use by the [sqlite3_vfs|VFS interface] only, and not
3513 ** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is
3555 ** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the
3573 ** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag.
4059 ** <dd>The SQLITE_PREPARE_PERSISTENT flag is a hint to the query planner
4061 ** probably reused many times.)^ ^Without this flag, [sqlite3_prepare_v3()]
4070 ** <dd>The SQLITE_PREPARE_NORMALIZE flag is a no-op. This flag used
4075 ** flag.
4078 ** <dd>The SQLITE_PREPARE_NO_VTAB flag causes the SQL compiler
5250 ** of the [SQLITE_DETERMINISTIC] flag is recommended where possible.
5253 ** flag, which if present prevents the function from being invoked from
5257 ** For best security, the [SQLITE_DIRECTONLY] flag is recommended for
5262 ** Without this flag, an attacker might be able to modify the schema of
5386 ** The SQLITE_DETERMINISTIC flag means that the new function always gives
5397 ** The SQLITE_DIRECTONLY flag means that the function may only be invoked
5408 ** The SQLITE_INNOCUOUS flag means that the function is unlikely
5425 ** SQLITE_INNOCUOUS flag for application-defined functions unless the
5431 ** The SQLITE_SUBTYPE flag indicates to SQLite that a function may call
5433 ** Specifying this flag makes no difference for scalar or aggregate user
6659 ** with the [SQLITE_OPEN_SHAREDCACHE] flag.
7119 ** aConstraintUsage[].omit flag is an optimization hint. When the omit flag
7121 ** checked separately in byte code. If the omit flag is change to true, then
7123 ** when the omit flag is true there is no guarantee that the constraint will
7145 ** mask of SQLITE_INDEX_SCAN_* flags. Currently there is only one such flag -
7146 ** SQLITE_INDEX_SCAN_UNIQUE. If the xBestIndex method sets this flag, SQLite
7149 ** Additionally, if xBestIndex sets the SQLITE_INDEX_SCAN_UNIQUE flag, then
7677 ** ^Each new VFS becomes the default VFS if the makeDflt flag is set.
7680 ** with the makeDflt flag set. If two different VFSes with the
7899 ** with the SQLITE_DEBUG flag. External mutex implementations
8723 ** false will always have the "discard" flag set to true.
9542 ** flag unless absolutely necessary.
9636 ** the "orderByConsumed" flag.
9644 ** the xBestIndex method to set the "orderByConsumed" flag, regardless of
9679 ** specified above, then it must not set the "orderByConsumed" flag in the
9683 ** it wants, as long as the "orderByConsumed" flag is not set. ^When the
9684 ** the "orderByConsumed" flag is unset, the query planner will add extra
9686 ** ordered correctly. The use of the "orderByConsumed" flag and the
9689 ** flag might help queries against a virtual table to run faster. Being
9690 ** overly aggressive and setting the "orderByConsumed" flag when it is not
10440 ** free it when it has finished using it. Without this flag, the caller
10443 ** The SQLITE_DESERIALIZE_RESIZEABLE flag means that SQLite is allowed to
10445 ** flag should only be used if SQLITE_DESERIALIZE_FREEONCLOSE is also used.
10446 ** Without this flag, the deserialized database cannot increase in size beyond
10449 ** The SQLITE_DESERIALIZE_READONLY flag means that the deserialized database