Rowan Worth wrote:
> I do think it's worth a mention in the PRAGMA SYNCHRONOUS=0 documentation
> that sqlite3_close() doesn't propagate I/O errors so you might never hear
> about write failures in this mode.
When writing asynchronously, errors can be detected _after_ the close, so
this is not even
Hi guys,
Ran into an interesting case today where one of our programs was writing an
sqlite DB to a network file system. Just as it was finishing up there was a
brief connectivity issue, and sqlite's call to close() ran into an EIO
error.
Sqlite3_close() doesn't return an error in this case so it
2 matches
Mail list logo