On 1 April 2015 at 15:48, Vadim Zeitlin <vz-s...@zeitlins.org> wrote: > > I'd like to return to the following problem: currently, if an SQL query > fails, you often have no idea why exactly did it fail because you don't > have the values of its parameters. A typical example we have to deal with > is that the process importing some data files into the database stops with > an error like this: > > database exception: violation of PRIMARY or UNIQUE KEY constraint > "PK_FOO" on table "FOO" while executing "insert into foo(a, b, c) > values(:a, :b, :c)" > > This is singularly unhelpful because what the user really needs to know is > for what values of "a", "b" and "c" this violation happened as this would > allow to immediately locate the duplicate value(s) in the input. But SOCI > doesn't provide this information and without it finding the problem is very > difficult. > [...] > So I'd like to merge this a.s.a.p., please let me know if anybody has any > objections to this.
Apologies for delay, I've overlooked this message in my inbox. However, I'd like to acknowledge I'm happy to see your PR #302 merged. You have already merged it into the master, good.. Thanks for picking up the old topic and the efforts to get it done! Best regards -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ soci-users mailing list soci-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-users
