The return code from an sqlite function (also from sqlite3_errcode()) is very general, for example including many different conditions under SQLITE_ERROR.
However, the message returned from sqlite3_errmsg() does convey more information, so the detail is obviously there somewhere. But using this error message text to control program behaviour is not a good idea ! Specifically, in a programmatic schema update task, I would like to be able to differentiate between: ALTER TABLE tab ADD New TEXT - SQLITE_ERROR - no such table: tab and ALTER TABLE tab ADD New TEXT - SQLITE_ERROR - duplicate column name: New without having to resort to strstr(sqlite_msg, "duplicate column") But without a suitable extended error number, that is what I think is the only solution ... would be nice to have sqlite3_ext_errcode() to get a better view. (The existing extended error code system is restricted to I/O errors ...) Any better ideas ? Regards, MikeW _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
