-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
D. Richard Hipp wrote:
| All core features have been thoroughly tested. I'm looking for problems | with the API. Do we need new parameters on some functions? Do we need | to change the semantics of some functions?
Yes! I discoverd an issue with the error handling in sqlite3_column_name and sqlite3_column_decltype (Version 3.0.3 I think):
They return a null pointer, if the index is out of range. They don't set a error code in the sqlite3* data.
But, if sqlite3_column_blob/text/double/int are used with a wrong index they behave as the requested column data was NULL and they set a SQLITE_RANGE error.
In my opinion, sqlite3_column_name/decltype should it do the same way.
I.e. return an empty string ("") and set SQLITE_RANGE in the cases the
index was invalid.
Michael Roth
-----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBLbAdSIrOxc3jOmoRAlf/AKC1syGv0Wx0Jc0tWI0zQSuWC8vkDwCfZnRQ a8Bf7mLfCGjLlyIHXsE/sQo= =as6m -----END PGP SIGNATURE-----
