On 04 Apr 2016 at 17:36, Domingo Alvarez Duarte <sqlite-mail at dev.dadbiz.es> 
wrote: 

> Fair enough !
>
> But even then could it have let's say a place for record the last foreign key
> violation ?
>
> Only one place will be better than nothing, it can be overwritten every time
> a foreign key is found and at least we could have a message like this:

You can write your own wrapper to do this. I have 850 places in my app where I 
do query or exec, so in the event of failure I need to know which one and what 
the sql was. When a problem occurs I log this information.

--
Cheers  --  Tim

Reply via email to