On Fri, 25 Oct 2013 16:31:56 +0200, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: > 25.10.2013 16:17, Vlad Khorsun wrote: >> Also, i consider accompanied SQL CODE message >> >> The insert failed because a column definition includes >> validation constraints. >> >> is not good, as it is the same for both INSERT and UPDATE statements. >> I offer to change it by something like >> >> The insert (update) failed because a column definition includes >> validation constraints. >> >> or someone could offer better wording. >> >> Opinions ? > > Phrase "Column constraint violated" is shorter and provide the same > amount of information.
I agree, the current message is even nonsensical, because the insert (or update) did not fail because the column definition includes validation constraints, but because the insert violated one of those constraints. BTW: Would it be possible to include the name of the actual constraint that was violated? Mark ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
