From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
Date: Sun, 20 Feb 2011 08:48:21 +0100 (CET)
Message-ID: <alpine.DEB.2.00.1102200825550.2423@localhost6.localdomain6> (raw)
In-Reply-To: <201102200011.p1K0B1l06164@momjian.us>
References: <201102200011.p1K0B1l06164@momjian.us>
Hello Bruce,
>>>> Is that the direction we want to go, or would it be better to factor
>>>> the information out into a separate page about compatibility gotchas?
>>>
>>> It would probably be better to explain globally applicable issues in a
>>> separate section.
>>
>> I agree that a general caveat is better, together with a one line
>> reference in the documentation of each table with an issue.
>
> Oh, I just noticed this. Can you give me a list of information_schema
> tables that have this issue? I am only aware of
> referential_constraints.
Possibly any relation which references constraints with a (catalog,
schema, name) triplet expecting it to be unique should have this issue.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: coelho@cri.ensmp.fr, bruce@momjian.us, peter_e@gmx.net, tgl@sss.pgh.pa.us, alvherre@commandprompt.com
Subject: Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
In-Reply-To: <alpine.DEB.2.00.1102200825550.2423@localhost6.localdomain6>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox