Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0NLdql37803 for ; Wed, 23 Jan 2002 16:39:52 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 674429; Wed, 23 Jan 2002 13:39:51 -0800 From: "Josh Berkus" Subject: Re: "SQL" REPLACE SYNTAX To: Andrew McMillan , Vince Vielhaber Cc: Christopher Kings-Lynne , PostgresSQL PHPlist , Manuel Lemos X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Wed, 23 Jan 2002 13:39:51 -0800 Message-ID: In-Reply-To: <1011786105.2863.24.camel@kant.mcmillan.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200201/68 X-Sequence-Number: 872 Folks, You can propose this syntax additon on the pgsql-sql list, which exists to discuss these kinds of issues. However, I will warn you that the core developers have already rejected the REPLACE syntax once as an unnecessary deviation from the SQL92 standard. There was a long discussion following that rejection, sometime last summer I think, about how one could use triggers or rules to ape this functionality on an INSERT statement. See the pgsql-sql list archives. You can, of course, also write the ANSI committee and propose that REPLACE be added to SQL3. Good luck. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco