Built-In Scalar SQL Functions
(lang_corefunc.html)
... Because octet_length(X) returns the number of bytes in X, not the number
of characters, the value returned depends on the database encoding. The
octet_length() function can return different answers for the same input string
if the database encoding is ...
|
SQL Language Expressions
(lang_expr.html)
... TEXT
To cast a BLOB value to TEXT, the sequence of bytes that make up the
BLOB is interpreted as text encoded using the database encoding.
Casting an INTEGER or REAL value into TEXT renders the value as if via ...
|
C API: Function Flags
(c3ref/c_deterministic.html)
SQLITE_DETERMINISTIC, SQLITE_DIRECTONLY, SQLITE_SUBTYPE, SQLITE_INNOCUOUS, SQLITE_RESULT_SUBTYPE
These constants may be ORed together with the
preferred text encoding as the fourth argument
to sqlite3_create_function(), sqlite3_create_function16(), or
sqlite3_create_function_v2().
SQLITE_DETERMINISTIC
The SQLITE_DETERMINISTIC flag means that the new function always gives
the same output when the input parameters are the ...
|
C API: Compiling An SQL Statement
(c3ref/prepare.html)
sqlite3_prepare(), sqlite3_prepare_v2(), sqlite3_prepare_v3(), sqlite3_prepare16(), sqlite3_prepare16_v2(), sqlite3_prepare16_v3()
... The second argument, "zSql", is the statement to be compiled, encoded
as either UTF-8 or UTF-16. The sqlite3_prepare(), sqlite3_prepare_v2(),
and sqlite3_prepare_v3()
interfaces use UTF-8, and sqlite3_prepare16(), sqlite3_prepare16_v2(),
and sqlite3_prepare16_v3() use UTF-16.
If the nByte argument is ...
|
The C language interface to SQLite Version 2
(c_interface.html)
... Note that the character encoding mechanism used by SQLite cannot
be changed at run-time. This is a compile-time option only. The
sqlite_encoding character string just tells you how the library
was compiled.
3.8 Changing the library's ...
|
Appropriate Uses For SQLite
(whentouse.html)
... Content is encoded in a
well-defined, cross-platform, and stable file format.
The encoding is efficient, and receivers can extract small subsets
of the content without having to read and parse the entire file.
SQL archives are useful as ...
|
Database File Format
(fileformat.html)
1.3.13. Text encoding
The 4-byte big-endian integer at offset 56 determines the encoding
used for all text strings stored in the database.
A value of 1 means UTF-8.
A value of 2 means UTF-16le.
A value of 3 means ...
|
C API: Result Values From A Query
(c3ref/column_blob.html)
sqlite3_column_blob(), sqlite3_column_double(), sqlite3_column_int(), sqlite3_column_int64(), sqlite3_column_text(), sqlite3_column_text16 ...
... Strings returned by sqlite3_column_text16() always have the endianness
which is native to the platform, regardless of the text encoding set
for the database.
Warning: The object returned by sqlite3_column_value() is an
unprotected sqlite3_value object. In a multithreaded environment,
an unprotected ...
|
C/C++ Interface For SQLite Version 3 (old)
(capi3.html)
... sqlite3_column_bytes() returns
the number of bytes in a column that has type BLOB or the number of bytes
in a TEXT string with UTF-8 encoding. sqlite3_column_bytes16() returns
the same value for BLOBs but for TEXT strings returns the number ...
|
SQLite FTS3 and FTS4 Extensions
(fts3.html)
9.2. Variable Length Integer (varint) Format
Integer values stored as part of segment b-tree nodes are encoded using the
FTS varint format. This encoding is similar, but not identical, to
the SQLite varint format.
An encoded FTS varint consumes between one and ten bytes of ...
|
Page generated by FTS5 in about 44.28 ms.