Support for detailed description of errors cased by trigger-violations

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Support for detailed description of errors cased by trigger-violations
Date: 2014-11-08 20:16:31
Message-ID: VisenaEmail.5.79a588b4b5dcb1c1.14991095a24@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.   When working with Oracle it is possible to catch constraint-violations
caused by triggers using JDBC, but it seems this isn't possible using PG, see
this thread:
https://github.com/impossibl/pgjdbc-ng/issues/111#issuecomment-62276464   For
check of FK-violations the protocol supports this fine, with details about
which table, column etc. causing the violation. Is there any work going on or
are there any plans to support similar info for violations caused by triggers?  
Thanks.   -- Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56
963 andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com> www.visena.com
<https://www.visena.com> <https://www.visena.com>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Hernández Tortosa 2014-11-08 20:48:28 Re: Repeatable read and serializable transactions see data committed after tx start
Previous Message Josh Berkus 2014-11-08 20:10:48 Re: pg_multixact not getting truncated