![]() ![]() SQLITE_API sqlite3 *sqlite3_db_handle(sqlite3_stmt*) ** create the statement in the first place. ** to the call (or its variants) that was used to ** returned by sqlite3_db_handle is the same ^If V is a, then the result ** of sqlite3_value_dup(V) is a NULL value.** SQLITE_API void sqlite3_value_free(sqlite3_value*) SQLITE_API sqlite3_value *sqlite3_value_dup(const sqlite3_value*) ** then sqlite3_value_free(V) is a harmless no-op. ** ^The sqlite3_value_free(V) interface frees an object ** ^The sqlite3_value_dup(V) interface returns NULL if V is NULL or if a ** object D and returns a pointer to that copy. ** ^The sqlite3_value_dup(V) interface makes a copy of the ** BLOB TEXT to TEXT, ensure zero terminator ** Type conversions and pointer invalidations might occur ** sqlite3_column_text16() may be invalidated. ** calls to sqlite3_column_blob(), sqlite3_column_text(), and/or ** Note that when type conversions occur, pointers returned by prior ** BLOB TEXT Add a zero terminator if needed** ** FLOAT TEXT ASCII rendering of the float ** These routines may attempt to convert the datatype of the result. ** ** ^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.** ^(The following table details the conversions ** is requested, is used internally to perform the ** ^For example, if the internal representation is FLOAT and a text result ** The these routines may attempt to convert the datatype of the result. ** is normally only useful within the implementation of ** Hence, the sqlite3_column_value() interface ** is used in any other way, including calls ** an unprotected sqlite3_value object may only be used safely with ** Warning: ^The object returned by is an ** value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer. ** even empty strings, are always zero-terminated. ** ^Strings returned by sqlite3_column_text() and sqlite3_column_text16(), ** bytes in the string, not the number of characters. ** These interfaces provide the same information as the , ** KEYWORDS: sqlite3_version sqlite3_sourceid ** CAPI3REF: Run-Time Library Version Numbers ** four hexadecimal digits of the hash may be modified. ** been edited in any way since it was last checked in, then the last ![]() By combining all the individual C code files into this ** This file is all you need to compile SQLite. ** of 5% or more are commonly seen when SQLite is compiled as a single ** possible if the files were compiled separately. This allows many compilers to do optimizations that would not be ** single large file, the entire code can be compiled as a single translation ** This file is an amalgamation of many separate C source files from SQLite ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |