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-31 05:53:27 |
Message-ID: | CAKFQuwbPkW1YXq0WzqQaWQJR1OpcpF0gY7f69hR1TYgYch2wow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Monday, August 30, 2021, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Monday, August 30, 2021, Daniel Westermann (DWE) <
> daniel(dot)westermann(at)dbi-services(dot)com> wrote:
>
>>
>> >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.
>
>
> Create a second table and add a constraint of the same name to it.
>
>
And your error is actually because the name of the unique index backing the
constraint is a problem, not the name of the constraint itself. Try naming
a check constraint.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Pantelis Theodosiou | 2021-08-31 06:43:14 | Re: Wrong note in the information schema section? |
Previous Message | David G. Johnston | 2021-08-31 05:48:50 | Wrong note in the information schema section? |