Thank you. The problem is that when I close there are still I/O operations that sometimes need to happen, e.g. flush of some buffers, and I need to know if those operations finished successfully or not. For example, the close operation fails to flush some of the buffers reports an error that is discarded and the application wouldn't know there is something wrong with the DB.
I am not so sure why the error is discarded, even if I make sure the DB is consistent before the close (e.g. flush it to disk), there could be cases where the application may need to know if something wrong during xClose. With best regards, Adrian Dobrean 905-315-4953 -----Original Message----- From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Thursday, April 14, 2016 9:06 AM To: SQLite mailing list Subject: Re: [sqlite] sqlite3_close does not propagate the error from sqlite3_io_methods.xClose On 4/14/16, Dobrean, Adrian <adrian.dobrean at emc.com> wrote: > > Is there a way or what should be the proper way to capture the error > returned by sqlite3_io_methods.xClose? > No. It looks like the return value from sqlite3_io_methods.xClose is always ignored and discarded. Why is that a problem? -- 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
