| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Wrong note in the information schema section? |
| Date: | 2021-08-31 05:40:10 |
| Message-ID: | ZR0P278MB0920449BD329B7F7B69581FAD2CC9@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
>>..."This is because the SQL standard requires constraint names to be unique within a schema, but PostgreSQL does not enforce this >>restriction."
>>..
>>PostgreSQL does enforce unique constraint names in a schema:
>>[...]
>>... but I guess this is not what the notes is supposed to tell me, correct?
>Practically speaking there must be some level of scope where a duplicate name error can occur. All the docs say is that the schema >scope is not it. You've demonstrated that it is the table scope where duplication of names is detected.
Thanks, David. The sentence above is still misleading, at least according to my understanding.
Regards
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-08-31 05:48:50 | Wrong note in the information schema section? |
| Previous Message | Jonathan S. Katz | 2021-08-30 16:16:13 | Re: I came here to determine how much storage a boolean variable uses |