On 18 Apr 2017, at 6:01am, Brendan Duddridge <brend...@gmail.com> wrote:
> Perhaps the only think I can think of that I'm doing that may be unorthodox > is by storing the SQLite files inside a macOS package. But at the unix > layer that's really just a directory, so I don't know how that could cause > a problem. Unless macOS treats the package in a way differently than a > normal folder and is causing things to get moved around or written when a > power failure occurs. You should be safe storing a SQLite database inside a package. As you write, a package is really just a folder with one extra bit set. Any demonstration code which uses the SQLite API directly we can attempt to debug. If the problem you need solving is actually with Couchbase, you can solve it by upgrading to any version from 2.0 onwards. Since that no longer uses SQLite, SQLite database corruption can no longer be a problem. Current versions of Couchbase no longer use SQLite for a persistence layer and Couchbase developers are unlikely to assist with any problem you find with such an old version. If your program demonstrating the problem has access to the SQLite database solely via libsqlcrypt.a, can you explain what you’re using it for ? Is your database actually direct access to a Lotus Notes file ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
