| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(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-30 15:21:59 |
| Message-ID: | CAKFQuwYEJc4nF+=4J8d6z8DYs=b4zp-f9q9S5psReNM+OZ3N6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Aug 30, 2021 at 5:51 AM Daniel Westermann (DWE) <
daniel(dot)westermann(at)dbi-services(dot)com> wrote:
>
> we have this note in the information schema section, e.g. in
> https://www.postgresql.org/docs/current/information-schema.html
>
> ..."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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-08-30 15:31:04 | Re: I came here to determine how much storage a boolean variable uses |
| Previous Message | Daniel Westermann (DWE) | 2021-08-30 12:50:59 | Wrong note in the information schema section? |