On 3/17/15, Richard Hipp <drh at sqlite.org> wrote: > On 3/17/15, Simon Slavin <slavins at bigfraud.org> wrote: >> The first two sentences on this page >> >> <https://www.sqlite.org/c3ref/errcode.html> >> >> contradict one-another. Here they are: >> >> "The sqlite3_errcode() interface returns the numeric result code or >> extended >> result code for the most recent failed sqlite3_* API call associated with >> a >> database connection.
Modified copy found at https://www.sqlite.org/draft/c3ref/errcode.html > > "most recent" is intended to modify "sqlite3_* API" not "failed > sqlite3_* API". But I see how that can be ambiguous so I will find a > way to reword it. > > If a prior API call failed but the most recent API call >> succeeded, the return value from sqlite3_errcode() is undefined." >> >> Suppose there is the following pattern of usage: >> >> sqlite3_bind_int() -- fails with a result of SQLITE_RANGE >> sqlite3_bind_text() -- succeeds without problems. >> >> The first sentence says that the result code of sqlite3_errcode() will >> definitely be SQLITE_RANGE. The second sentence says that the result >> code >> of sqlite3_errcode() is undefined. >> >> Simon. >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > > > -- > D. Richard Hipp > drh at sqlite.org > -- D. Richard Hipp drh at sqlite.org
