From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | bruce(at)momjian(dot)us |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS |
Date: | 2011-02-22 14:07:39 |
Message-ID: | 201102221407.p1ME7dA17560@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
bruce wrote:
>
> I have moved the text about duplicate constraints to the top of the
> information schema section because it affects several tables (applied
> patch attached). I could not figure out how to get the actual error
> concept to the front of the paragraph.
I found a way to reword the paragraph to be clearer about its purpose:
When querying the database for constraint information, it is possible
for a standard-compliant query that expects to return one row to
return several. This is because the SQL standard requires constraint
names to be unique within a schema, but
<productname>PostgreSQL</productname> does not enforce this
restriction. <productname>PostgreSQL</productname>
automatically-generated constraint names avoid duplicates in the
same schema, but users can specify such duplicate names.
Applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-02-22 16:56:18 | Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS |
Previous Message | Bruce Momjian | 2011-02-22 01:15:14 | Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS |