On 25-10-2013 17:50, Vlad Khorsun wrote: >>>> BTW: Would it be possible to include the name of the actual constraint >>>> that was violated? >>> >>> CREATE TABE T >>> ( >>> F1 INT NOT NULL, >>> F2 INT CHECK(F2 >= 0) >>> ) >>> >>> what constraint name would you like to report in both cases ? :) >> >> Doesn't that get assigned an internal name (I honestly don't remember and >> I don't have Firebird at hand to check)? > > NOT NULL constraints have such name and other constraints implemented > using system triggers and have names like CHECK_NNN. Are you sure it will > be really useful to show such name ?
I just looked it up and CHECK constraints can also be explicitly named by the user, so either the user gets the system generated name or the specified name. Mark -- Mark Rotteveel ------------------------------------------------------------------------------ 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
