Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 41E08475892 for ; Tue, 26 Feb 2002 16:08:32 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 810826; Tue, 26 Feb 2002 13:08:28 -0800 From: "Josh Berkus" Subject: Re: About referential integrity. To: David BOURIAUD , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Tue, 26 Feb 2002 13:08:28 -0800 Message-ID: In-Reply-To: <200202260753.g1Q7rdx22057@necker.ac-rouen.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200202/411 X-Sequence-Number: 6833 David, > Anyway, couldn't it be an extention to postgreSQL ? If you have heard > about > Business Objects, you should know that it can do it very well > provided you > draw the relationchips between the tables of your database. And it's > of much > use, since you just have to concentrate on the fields you want to > fetch and > the program takes care of the relations and handles group by, order > by and > where clause. Certainly it could. However, the project needs a really persuasive reason to transgress the SQL standard. That is, substantial funcitonality needs to be gained from the extension, sufficient to offset the issues raised with porting applications to and from Postgresql. However, there appears to be a way to give you what you want without violating the standard: we could make Natural Join work for foriegn-keyed columns, not just columns with similar names. This would give us some useful funcitionality without breaking the standard. I understand from Stephan that there is some technical problem with this, but we could add it to the TODO list, yes? -Josh Berkus