On 23 Apr 2019, at 12:32am, Lee, Jason <jason...@lanl.gov> wrote: > The current code is effectively just an sqlite3_open_v2 followed by an > sqlite3_close
Then either your code is faulty, and doesn't actually do this, or your problem has nothing to do with SQLite. SQLite doesn't open a database file when you use sqlite3_open_v2(). It doesn't even see whether the file, or even the path, exists. The file is opened only when you use an API function which needs to read or write the file. _open() followed by _close() just uses up a little memory to store the file path and some other settings, then releases it again. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users