Postgres Pro
Downloads
Home   >   mailing lists

Support for detailed description of errors cased by trigger-violations - Mailing list pgsql-hackers

From Andreas Joseph Krogh
Subject Support for detailed description of errors cased by trigger-violations
Date
Msg-id VisenaEmail.5.79a588b4b5dcb1c1.14991095a24@tc7-visena
Whole thread Raw
Responses Re: Support for detailed description of errors cased by trigger-violations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view
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
Attachment

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_multixact not getting truncated
Next
From: Álvaro Hernández Tortosa
Date:
Subject: Re: Repeatable read and serializable transactions see data committed after tx start