On 2 Feb 2017, at 11:08am, x <[email protected]> wrote:
> Thanks for the reply Simon but the wrapper throws an exception if either
> reset or finalize fails to return SQLITE_OK so not that.
Okay. So your question boils down to whether the second _prepare() in this is
legal:
_open()
_prepare()
_step()
_reset()
_prepare()
_step()
_reset()
_close()
and you’re getting an error returned on _close() rather than on the _prepare()
itself.
The documentation doesn’t seem to say whether it’s legal or not, but I feel
that if it isn’t, you should be getting SQLITE_MISUSE returned from the second
_prepare().
You appear to be doing appropriate error-trapping. I’m out of ideas but I hope
with that restatement of your problem someone else can help you.
Simon.
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users