On 12 Mar 2019, at 9:41pm, Ted Goldblatt <[email protected]> wrote:
> SQLITE_OMIT_xxx, SQLITE_DEFAULT_CACHE_SIZE, > SQLITE_THREADSAFE None of these are a problem, assuming your embedded app does not do multi-threading. > One of these is SQLITE_TEMP_STORE, which is set to > "Always use memory" which strikes me a suspicious relative to a power fail > problem. That's fine. It just means that using memory is 'cheaper' to that embedded app than using backing store. Losing power while temporary storage is in use won't suffer from that setting. > The DB opens are directly by CppSQLite3 (which uses > sqlite_open_v2()), and all of those calls have OPEN_READONLY or > OPEN_READWRITE as the 3rd param and 0 as the 4th. The CppSQLite3 methods > themselves take only a filename. Good. No shared memory, or messing with caching, or disabling of locking. <https://sqlite.org/uri.html> > It doesn't appear that any PRAGMAs appear outside the CppSQLite3_16.cpp > and sqlite3.h files. It seems very unlikely that a general-purpose C++ wrapper would set any setting to increase the possibility of corruption. So that's good too. Okay, I clear you for all the above. As far as I can tell, your software doesn't intentionally disable any of SQLite's safety measures. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
