C API: Setting The Subtype Of An SQL Function
(c3ref/result_subtype.html)
sqlite3_result_subtype()
... Every application-defined SQL function that invokes this interface
should include the SQLITE_RESULT_SUBTYPE property in its
text encoding argument when the SQL function is
registered. If the SQLITE_RESULT_SUBTYPE
property is omitted from the function that invokes sqlite3_result_subtype(),
then in some ...
|
SQLite Version 3 Overview
(version3.html)
... Separate implementations can be registered
for each encoding. If an SQL function or collating sequence is required
but a version for the current text encoding is not available, then
the text is automatically converted. As before, this conversion takes
computation ...
|
C API: Collation Needed Callbacks
(c3ref/collation_needed.html)
sqlite3_collation_needed(), sqlite3_collation_needed16()
... If the function is registered using the sqlite3_collation_needed() API,
then it is passed the names of undefined collation sequences as strings
encoded in UTF-8. If sqlite3_collation_needed16() is used,
the names are passed as UTF-16 in machine native byte ...
|
C API: Declared Datatype Of A Query Result
(c3ref/column_decltype.html)
sqlite3_column_decltype(), sqlite3_column_decltype16()
... The returned string is always UTF-8 encoded.
For example, given the database schema:
CREATE TABLE t1(c1 VARIANT);
and the following statement to be compiled:
SELECT c1 + 1, c1 FROM t1;
this routine would return the string "VARIANT" for ...
|
C API: Binding Values To Prepared Statements
(c3ref/bind_blob.html)
sqlite3_bind_blob(), sqlite3_bind_blob64(), sqlite3_bind_double(), sqlite3_bind_int(), sqlite3_bind_int64(), sqlite3_bind_null ...
... If
the sixth argument to sqlite3_bind_text64() is not one of the
allowed values shown above, or if the text encoding is different
from the encoding specified by the sixth parameter, then the behavior
is undefined.
The sqlite3_bind_zeroblob() routine binds a ...
|
C API: Opening A New Database Connection
(c3ref/open.html)
sqlite3_open(), sqlite3_open16()
... The default encoding will be UTF-8 for databases created using
sqlite3_open() or sqlite3_open_v2(). The default encoding for databases
created using sqlite3_open16() will be UTF-16 in the native byte order.
Whether or not an error occurs when it is ...
|
Floating Point Numbers
(floatingpoint.html)
2.1.3. The ieee754_from_blob() and ieee754_to_blob() functions
The ieee754_to_blob(F) SQL function converts the floating point number F
into an 8-byte BLOB that is the big-endian binary64 encoding of that number.
The ieee754_from_blob(B) function goes the other way, converting an 8-byte
blob into ...
|
Pragma statements supported by SQLite
(pragma.html)
PRAGMA encoding
PRAGMA encoding;
PRAGMA encoding = 'UTF-8';
PRAGMA encoding = 'UTF-16';
PRAGMA encoding = 'UTF-16le';
PRAGMA encoding = 'UTF-16be';
In first form, if the main database has already been
created, then this pragma returns the text encoding used by the
main ...
|
C API: One-Step Query Execution Interface
(c3ref/exec.html)
sqlite3_exec()
... The sqlite3_exec() interface runs zero or more UTF-8 encoded,
semicolon-separate SQL statements passed into its 2nd argument,
in the context of the database connection passed in as its 1st
argument. If the callback function of the 3rd argument ...
|
C API: Setting The Result Of An SQL Function
(c3ref/result_blob.html)
sqlite3_result_blob(), sqlite3_result_blob64(), sqlite3_result_double(), sqlite3_result_error(), sqlite3_result_error16(), sqlite3_result_error_toobig ...
... The sqlite3_result_text64() interface sets the return value of an
application-defined function to be a text string in an encoding
specified by the fifth (and last) parameter, which must be one
of SQLITE_UTF8, SQLITE_UTF16, SQLITE_UTF16BE, or SQLITE_UTF16LE.
SQLite takes the ...
|
Page generated by FTS5 in about 45.70 ms.