On Fri, 8 Feb 2019 at 20:03, Theodore Dubois <tbl...@icloud.com> wrote:
> I'd like to essentially commit changes to disk in the middle of the > transaction, resulting in a transaction that is atomic with respect to > other database connections but is two atomic transactions with respect to > the filesystem. > "atomic transaction with respect to the filesystem" doesn't really make sense to me - from a filesystem perspective all you have is a bunch of changes to various data blocks, and a sync(). Why does it matter to you that changes are on-disk mid-transaction? What are the actual semantics you're hoping to implement? -Rowan _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
