Just to be clear Situation: Under Linux/Debian, Sqlite opens an entirely valid DB, and runs an entirely valid SQL transaction against that database. Following a Commit, the application gets back a 'Commit Successful' code. (Ignore any issues of disks returning hardware 'write done' flags prematurely). There is then a power/OS failure.
Using the standard defaults (which avoid WAL), is there any possibility whatsoever of that last SQL transaction being lost? Best regards On Mon, Jan 25, 2016 at 8:39 PM, Richard Hipp <drh at sqlite.org> wrote: > On 1/25/16, Howard Chu <hyc at symas.com> wrote: > > > > This is actually quite an unusual requirement; on older Unix systems you > > couldn't even *open* a directory, let alone obtain write access to it or > > fsync it. > > Yeah. When the SQLITE_DISABLE_DIRSYNC compile-time option is present, > we disable the directory sync logic for this reason. Some unixes > (HP/UX) require -DSQLITE_DISABLE_DIRSYNC in order to work. But Linux, > MacOS, and *BSD all work without it, so I thought I'd just not bring > that up... > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
