| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: issue about information_schema REFERENTIAL_CONSTRAINTS (resent) |
| Date: | 2010-09-03 18:05:24 |
| Message-ID: | alpine.DEB.2.00.1009032004270.2622@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> If you're going to use something which is PostgreSQL-specific, you may as
> well write your own views or use the "native" tables and views directly.
I wish I could write portable code, if possible:-)
I'm basically writing views on top of the information_schema under the
assumption that what is expected to be a key is a key. The information schema
is *useless* otherwise as wrong tuples are built on join, and derived
information is not reliable.
I guess I must the only actual user of the information_schema, and it will soon
be back to zero user, which will be fine from the developers point of view.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-03 21:55:15 | Re: BUG #5633: an empty row with null-like values in not-null field |
| Previous Message | Fabien COELHO | 2010-09-03 17:53:48 | Re: issue about information_schema REFERENTIAL_CONSTRAINTS |