Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 4463C6329C0
	for <pgsql-bugs-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 14:55:48 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 95145-10 for
	<pgsql-bugs-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 17:55:41 +0000 (UTC)
X-Greylist: delayed 00:05:29.7744 by SQLgrey-1.7.6
Received: from cascavel.ensmp.fr (cascavel.ensmp.fr [194.214.158.227])
	by mail.postgresql.org (Postfix) with ESMTP id 258BD6323FE
	for <pgsql-bugs@postgresql.org>; Fri,  3 Sep 2010 14:55:40 -0300 (ADT)
Received: from cri.ensmp.fr (85.40.219-88.rev.gaoland.net [88.219.40.85] (may
	be forged)) (authenticated bits=0)
	by cascavel.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id
	o83Ho72X019312
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 3 Sep 2010 19:50:08 +0200 (MEST)
Date: Fri, 3 Sep 2010 19:50:07 +0200 (CEST)
From: Fabien COELHO <fabien.coelho@ensmp.fr>
X-X-Sender: fabien@localhost.localdomain
Reply-To: Fabien COELHO <fabien.coelho@ensmp.fr>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
cc: PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
In-Reply-To: <4C80CA8B020000250003517B@gw.wicourts.gov>
Message-ID: <alpine.DEB.2.00.1009031939250.2622@localhost.localdomain>
References: <alpine.DEB.2.00.1008311337530.2449@localhost.localdomain>
	<2683.1283266019@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009011557480.2570@localhost.localdomain>
	<1283369900.15386.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009020741380.2656@localhost.localdomain>
	<1283438419.23199.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009021959070.2656@localhost.localdomain>
	<6462.1283454730@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009031348321.2448@localhost.localdomain><alpine.DEB.2.00.1009031348321.2448@localhost.localdomain>
	<22801.1283525905@sss.pgh.pa.us>
	<4C80CA8B020000250003517B@gw.wicourts.gov>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Miltered: at cascavel with ID 4C81354F.000 by Joe's j-chkmail (http : //
	j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4C81354F.000 from
	[88.219.40.85]/85.40.219-88.rev.gaoland.net/88.219.40.85/cri.ensmp.fr/<fabien.coelho@ensmp.fr>
X-Scores-Stats: 4C81354F.000 B=0.03028 L=0.17721 G=0.00668 Agree    
X-j-chkmail-Score: MSGID : 4C81354F.000 on cascavel.ensmp.fr : j-chkmail score
	: . : R=. U=. O=. B=0.007 -> S=0.008
X-j-chkmail-Status: Ham
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201009/32
X-Sequence-Number: 27996


> 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.