When a SQL parsing error happens, the message returned by sqlite3_errmsg() is pretty terse... is there some way to retrieve more context, so that the user has more than one token to help locate the problem?
For example, having the previous several tokens that were successfully parsed would give a better idea of where to look for the SQL error. Thanks Erik ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
