| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: enhanced error fields |
| Date: | 2012-12-29 21:31:49 |
| Message-ID: | CAEYLb_UoYzhot=LdP4gum9HsxFPofEbzoMDUhrHQiErmoRfBtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29 December 2012 21:24, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> can we remove CONSTRAINT_NAME from this patch? Minimally TABLE_SCHEMA,
> TABLE_NAME and COLUMN_NAME works as expected.
>
> CONSTRAINT_NAME can be implemented after constraints refactoring
This patch is almost completely pointless without a CONSTRAINT_NAME field.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2012-12-29 22:57:04 | Re: enhanced error fields |
| Previous Message | Peter Geoghegan | 2012-12-29 21:30:53 | Re: enhanced error fields |