MikeW <[EMAIL PROTECTED]> writes: ... > 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 >
Having looked at the source code, looks like the best way to do this /would/ be to add another (!) numerical parameter to sqlite3ErrorMsg() indicating the extended error code that corresponds with the message. This code could then be returned as part of the error value in the standard way. (And maybe from a new function that allowed you to just get the extra detail.) But it's too much work to do, just for this one job, sadly ... MikeW _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
