Gentlemen,
Thank you for your replies. The definitive answers are helpful.
However,
there seems to be some confusion around the question.
RE: "simple enough to test" and "...see what happens..."
empirical analysis of basic reliability issues is insufficient
when
one is building an application for which one will be accountable
to
end-users that are relying on the application to do valuable
work.
I need to KNOW what SQLite does so that I can design around that
behaviour, not what I observe that it does.
RE: "Doctor, it hurts..."
this seems to imply that the question does not warrant analysis.
that
is incorrect. such scenarios can occur. if I were to ask the
question,
I would have been seeking to understand how SQLite copes with it
so
so that the application in question can be written to that
specification.
Whether or not another DB SW can recover from it is
uninteresting,
particularly in that context. that being the case, I suspect
that
SQLite will return an SQLITE_IOERROR (something from the
SQLITE_IOERROR* family).
-rlehr
Robert Lehr
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
