From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |
Date: | 2010-09-05 18:47:43 |
Message-ID: | 1283712463.12666.7.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
On fre, 2010-09-03 at 13:53 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Excerpts from Fabien COELHO's message of vie sep 03 13:39:19 -0400 2010:
> >> I tried to explained that I'm analyzing other people's schemas. I cannot
> >> ask all other people on the planet to rewrite their schemas, I pick them
> >> as they are.
>
> > Maybe you shouldn't be using the information_schema in the first place.
>
> It would probably be reasonable to put something into chapter 34 of the
> docs pointing out this limitation. I'm not sure exactly where though.
> Should we invent a "compatibility issues" section in that chapter,
> analogous to the ones we have for individual SQL commands? Are there
> other issues worth documenting for the information_schema views?
A very similar issue is already documented here:
http://developer.postgresql.org/pgdocs/postgres/infoschema-triggers.html
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-06 02:16:57 | Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS |
Previous Message | Tom Lane | 2010-09-05 15:27:27 | Re: BUG #5644: Selecting ROW() in variable with 9.0 not compatible with 8.4 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-06 02:16:57 | Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS |
Previous Message | Fabien COELHO | 2010-09-03 17:53:48 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |