Hello,
On 2016-04-14 16:16, Dobrean, Adrian wrote:
> Is xSync guaranteed to be called only once, same as for xClose, if it is then
> from flush I/O point of view we should be almost no difference.
No --- it is not guaranteed even once, as I described in previous post.
> However still xClose
Hello,
On 2016-04-14 15:40, Richard Hipp wrote:
> On 4/14/16, Dobrean, Adrian wrote:
>>
>> 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.
> This
users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp
Sent: Thursday, April 14, 2016 9:41 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 wrote:
>
> The problem is that when I close there are stil
: [sqlite] sqlite3_close does not propagate the error from
sqlite3_io_methods.xClose
On 4/14/16, Dobrean, Adrian 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 retur
Hi,
It looks like the error returned by sqlite3_io_methods.xClose is not propagated
all the way to sqlite3_close caller.
According to a comment in sqlite3_close this function (excepting SQLITE_BUSY)
always returns true.
Is there a way or what should be the proper way to capture the error
On 4/14/16, Dobrean, Adrian wrote:
>
> 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.
This shouldn't ever come up. xSync should have been called
On 4/14/16, Dobrean, Adrian wrote:
>
> I am not so sure why the error is discarded,
Because (1) failure is impossible on most implementations of xClose
and nearly so for the rest, and (2) propagating the error back up to
the application would require a lot of code that needs to be written,
On 4/14/16, Dobrean, Adrian 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
8 matches
Mail list logo
