Int (*xSavepoint)(sqlite3_vtab *pVTab, int) * The methods above are in version 1 of the sqlite_module object. Int (*Rename)(sqlite3_vtab *pVtab, const char *zNew) Void (**pxFunc)(sqlite3_context*,int,sqlite3_value**),
Int (*xFindFunction)(sqlite3_vtab *pVtab, int nArg, const char *zName, Int (*xUpdate)(sqlite3_vtab *, int, sqlite3_value **, sqlite_int64 *) Int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid) Int (*xColumn)(sqlite3_vtab_cursor*, sqlite3_context*, int) Int (*xFilter)(sqlite3_vtab_cursor*, int idxNum, const char *idxStr, Int (*xOpen)(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor) Int (*xBestIndex)(sqlite3_vtab *pVTab, sqlite3_index_info*) The virtual table implementation only needs to worry about freeing the zErrMsg content when it overwrites the content with a new, different error message.
#Sqlpro for sqlite index free
The SQLite core will free and zero the content of zErrMsg when it delivers the error message text to the client application or when it destroys the virtual table. Failure to do this will result in a memory leak.
Prior to assigning a new value to zErrMsg, the virtual table implementation must free any preexisting content of zErrMsg using sqlite3_free(). Space to hold this error message string must be obtained from an SQLite memory allocation function such as sqlite3_mprintf() or sqlite3_malloc(). The virtual table implementation may pass error message text to the core by putting an error message string in zErrMsg. The nRef field is used internally by the SQLite core and should not be altered by the virtual table implementation. Virtual table implementations will normally subclass this structure to add additional private and implementation-specific fields.
0 kommentar(er)
