Skip site navigation (1) Skip section navigation (2)

Re: issue about information_schema REFERENTIAL_CONSTRAINTS

From: Fabien COELHO <fabien(dot)coelho(at)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
Date: 2010-09-03 17:50:07
Message-ID: alpine.DEB.2.00.1009031939250.2622@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-docs
> 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.

In response to

Responses

pgsql-docs by date

Next:From: Tom LaneDate: 2010-09-03 17:53:26
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Previous:From: Alvaro HerreraDate: 2010-09-03 17:45:02
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-09-03 17:53:26
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Previous:From: Alvaro HerreraDate: 2010-09-03 17:45:02
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group