On Sep 14, 2011, at 3:14 PM, Simon Slavin wrote: >> Your exact text may not work to generate exactly the error you expect, but >> you should find something similar. > > That's the crux of the issue, as the constraint name is lost, even though the > constraint itself is implemented. Net loss of information. > Bummer > :( > > There is a ticket related to this issue, languishing, unloved and unresolved, > for many moons: > > http://www.sqlite.org/src/tktview?name=23b2128201 > http://www.sqlite.org/cvstrac/tktview?tn=1648
Yes, I too encountered this issue shortly after I started working with SQLite last year, and I too was disappointed at the lack of attention the ticket had received. Someone did post code enhancement/fix somewhere in one of those tickets, but I've not looked at that code, because we're not quite into modifying SQLite's source (yet). >From a relatively recent e-mail thread on this topic, my understanding is that >dredging up the actual constraint name for the message would take a lot of >effort (code), and that that is antithetical to the "lite-ness" of SQLite. Confidentiality Notice. This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
