I have this bit of code I've had around forever, I recently enabled SQLITE_CONFIG_LOG and have been getting a misuse because I'm calling sqlite3_config after initialization.
The one I'm calling is SQLITE_CONFIG_GETMALLOC which should read the internal routines already in use; I then override some of those in the sqlite3_mem_methods structure and set sqlite3_db_config to set those on a specific connection. The first thing in sqlite3_config is 'if( sqlite3GlobalConfig.isInit ) return SQLITE_MISUE-BKPT' shouldn't I be able to use config to read things? There is no check to see if the op is a write config or a read config.... _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
