Received: from traven.uol.com.br (traven.uol.com.br [200.231.206.184]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0N5RXl15983 for ; Wed, 23 Jan 2002 00:27:34 -0500 (EST) (envelope-from mlemos@acm.org) Received: from acm.org ([200.221.72.147]) by traven.uol.com.br (8.9.1/8.9.1) with ESMTP id DAA28498; Wed, 23 Jan 2002 03:16:48 -0200 (BRST) Message-ID: <3C4E4976.E0C4EE5A@acm.org> Date: Wed, 23 Jan 2002 03:26:14 -0200 From: Manuel Lemos X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Kings-Lynne CC: Francisco Reyes , PostgresSQL PHP list Subject: Re: "SQL" REPLACE SYNTAX References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200201/58 X-Sequence-Number: 863 Hello, Christopher Kings-Lynne wrote: > > > Actually only two: a SELECT and a depending on that, a INSERT or an > > UPDATE. You may want to try to look at Metabase implementation to see > > how it works. > > Read my previous post. How does MetaBase know which fields are the primary > key!?!?!?!? Look at Metabase implementation. Metabase comes with a driver conformance test that verifies if features like this work properly in all supported databases. Don't you think that I would release a version of Metabase that would not pass that test if all databases? The application needs to hint it as it is something that does not change at runtime, so there is no penalty of figuring that by querying the database server and some database do not provide a way to tell you which fields are the primary key. Regards, Manuel Lemos