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 ... 

sqlite3_create_collation(), sqlite3_create_collation_v2(), sqlite3_create_collation16()

 ... The eTextRep argument determines the encoding of strings passed to the collating function callback, xCompare. The SQLITE_UTF16 and SQLITE_UTF16_ALIGNED values for eTextRep force strings to be UTF16 with native byte order. The SQLITE_UTF16_ALIGNED value for eTextRep forces strings to begin ... 

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 ... 

 ... 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 ... 

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 ... 

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 ... 

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 ... 

2. Features  ... If the argument to base64() is a BLOB, then the return value is TEXT that is the RFC 4648 encoding of that BLOB. If the argument to base64() is base64 TEXT then the return value is a BLOB that is ... 

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 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 ...