From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |
Date: | 2010-09-03 17:39:19 |
Message-ID: | alpine.DEB.2.00.1009031920460.2622@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
>> Well, one must choose between to evil:
>
> Yeah, exactly. I think that the current tradeoff is just fine.
Hmmm. I think exactly the contrary. There is no point in having a non
reliable feature.
ISTM that very few people use the information schema, and if the query
results is not reliable, it will stay this way. If you have zero user, no
one will complain, which prooves that everything is fine:-) QED.
By the way, do you use the information schema?
> If you want SQL-standard behavior, pick SQL-standard constraint names,
> and there you are.
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.
Could you register this "bug" somewhere please?
Thanks for your time.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-09-03 17:45:02 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |
Previous Message | Kevin Grittner | 2010-09-03 15:14:35 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-09-03 17:45:02 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |
Previous Message | Kevin Grittner | 2010-09-03 15:14:35 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |