On 11/18/2015 15:33, Scott Hess wrote: > What do you plan to use the error message for? There is generally no > interface contract with error messages, so you can't generally depend on > them being readable by code. They are helpful to the developer, but > usually they just save you a few minutes figuring it out yourself. I'm not > hating on your few minutes, but saving a few milliseconds or bytes at > runtime on a few million devices is worth a periodic few minutes of my > time. You can use SQL to generate pretty complicated schema and queries, > so in the limit this kind of problem can be pretty deep to resolve!
I have a process that imports some data with quite complex structure. Every once in a while the constraint violation occurs (usually due to the data irregularities). Even this simple matter can be complicated when you are busy with 100s other things, and this DB schema isn't on top of your mind. My concern is mostly development time and to minimize the number of things to remember. So if the message can be more informative, I always vote for this. > Maybe it would make sense to have some sort of > SQLITE_WITH_EXTENDED_FK_ERRORS type define so that you can get a better > edit/compile/run loop going in development, without being expensive in > production. Yes, such option can very nicely become a package option (on BSD). Yuri
