| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Benjamin Coutu <ben(dot)coutu(at)zeyos(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Domain Constraint Violation Error Messages |
| Date: | 2018-07-25 16:54:36 |
| Message-ID: | 5768.1532537676@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-07-25 17:51:21 +0200, Benjamin Coutu wrote:
>> Well, the problem is that the underlying column is not referenced, and neither is the table. That's the issue right there.
> True. I didn't yet have my first coffee, sorry for that :). I think
> it'd possibly not be too hard to add support for naming the TABLE. Would
> that already be helpful enough for you?
I think we'd be better off casting this as a more generic "report the
location of execution-time errors" issue. See previous discussions
such as
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Coutu | 2018-07-25 17:45:21 | Re: Domain Constraint Violation Error Messages |
| Previous Message | Andres Freund | 2018-07-25 16:35:21 | Re: Domain Constraint Violation Error Messages |