Roger Binns <[EMAIL PROTECTED]> writes: > > > MikeW wrote: > > 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. > > http://www.sqlite.org/cvstrac/tktview?tn=3456 > > Roger >
Thanks Roger ! I also thought of a semi-kludge that prefixed an error code "character" greater than 0x7F say, to the beginning of each string, using string catenation, (#define SQLITE_EXT_ERR_MISC "\x82" ... sqlite3ErrorMsg(SQLITE_EXT_ERR_MISC "Misc error", ... ) Then sqlite3ErrorMsg() could retain the first byte as an error code if it was > 0x7F and skip on one char to get the text. This would allow retrofitting of codes gradually. BUT - it's a kludge, so I await the 'developers' to address the issue that you refer to. Cheers, MikeW _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
