On 17 Oct 2011 at 10:00, Jean-Christophe Deschamps <j...@antichoc.net> wrote:
> At least it would gives a fairly good hint as to what to look for and > where to look. You know that some extension function was passed an > out-of-range argument during the course of the last operation. From > there, tracking down the culprit is much easier. > > Anyway the issue to solve is not "which library issued it" but "what > extension function in the few last statements could have got invalid > argument[s]". The current situation is way too vague and leaves you > dry about the cause. With 350 calls in my code to query and exec, this is why I have a wrapper around them to include a location code, so that error logging can tell me straight away which call had the error and what was the SQL statement it was trying. -- Cheers -- Tim
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
