-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The functions sqlite3_status and sqlite3_db_status do substantially the same thing (in different scopes) and have exactly the same signature and semantics.
However the error code they return is gratuitously different when provided with a (currently unknown) code. In particular sqlite3_status returns SQLITE_MISUSE while sqlite3_db_status returns SQLITE_ERROR. It would be appropriate to make them return the same error code and for it to be SQLITE_NOTFOUND (just like file control uses). The doc doesn't currently specify which codes would be returned, but the current behaviour is very ambiguous. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlBFQyEACgkQmOOfHg372QTddwCdFiZCPjTvq6wZCRcX7f6A3Hri 1x0An2FmAFatiJ+m7dEGa1+8mdzZlrTw =P9kg -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
