| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, 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 20:07:01 |
| Message-ID: | CAFj8pRD6x1mRPgo4evQmhOPjy14UYsXowi3Gx_tm=8zfmTK63w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2012/12/29 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Pavel Stehule (pavel(dot)stehule(at)gmail(dot)com) wrote:
>> > Having just constraint_schema and constraint_name feels horribly wrong
>> > as the definition of a constraint also includes a pg_class oid.
>>
>> but then TABLE_NAME and TABLE_SCHEMA will be defined.
>
> How are you going to look up the constraint? Using constraint_schema,
> table_name, and constraint_name? Or table_schema, table_name and
> constraint_name? When do you use constraint_schema instead of
> table_schema?
>
> None of those options is exactly clear or understandable...
probably there will be situation when TABLE_SCHEMA and
CONSTRAINT_SCHEMA same values
Hypothetically - if we define CONSTRAINT_TABLE - what is difference
from TABLE_NAME ?
Pavel
>
> Thanks,
>
> Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2012-12-29 20:10:00 | Re: Patch for checking file parameters to psql before password prompt |
| Previous Message | Stephen Frost | 2012-12-29 20:00:51 | Re: enhanced error fields |