Received: from ginsberg.uol.com.br (ginsberg.uol.com.br [200.231.206.26]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0N4e3l08223 for ; Tue, 22 Jan 2002 23:40:04 -0500 (EST) (envelope-from mlemos@acm.org) Received: from acm.org ([200.221.72.147]) by ginsberg.uol.com.br (8.9.1/8.9.1) with ESMTP id CAA12631; Wed, 23 Jan 2002 02:39:01 -0200 (BRST) Message-ID: <3C4E3E7A.A48929A4@acm.org> Date: Wed, 23 Jan 2002 02:39:22 -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/55 X-Sequence-Number: 861 Hello, Christopher Kings-Lynne wrote: > > > We can discuss names, till the cows come home, but basically Manuel > > described what he meant. The "replace" functionality is one of the few > > things I liked of MySQL when I researched which dB to go with. The fact > > that this layer can abstract the functionality is a great point in my > > opinion. > > Here's an idea: look at their code to see what kind of SQL jiggery pokery > they needed to implement it and then implement it ourselves... > > BTW, from my estimates you'd need at least 4 - 6 sql queries to simulate the > REPLACE syntax for Postgres, so why on earth would you use it? 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. Regards, Manuel Lemos