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 g0M524l34374 for ; Tue, 22 Jan 2002 00:02: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 DAA28563; Tue, 22 Jan 2002 03:01:01 -0200 (BRST) Message-ID: <3C4CF22B.DDEB93AE@acm.org> Date: Tue, 22 Jan 2002 03:01:31 -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: PHP Abstraction layers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200201/42 X-Sequence-Number: 848 Hello, Christopher Kings-Lynne wrote: > > > A new release of Metabase was made just yesterday. It provides some > > features that users were requesting like the ability to customize error > > handling. It also provides yet another innovating features, which is the > > SQL REPLACE implementation. This is a statement like SQL INSERT except > > that if the values of the primary keys match the ones of an existing > > row, it will update that row instead of inserting a new one. AFAIK, only > > MySQL provides SQL REPLACE command, but Metabase provides a suitable > > emulation that works the same way using transactions so it works also > > with PostgreSQL, Oracle, MS-SQL server, Informix, Interbase, etc.. > > *cough* Callling it 'SQL REPLACE' is a bit of a misnomer. It is not > specified anywhere in the SQL standard. (Like lots of MySQL stuff) Still it is a good thing (tm). SQL standard is also a bit misnomer because every database vendor ships its own extensions and its own non-standard compliant quirks. My favourite is that Oracle stores empty strings in VARCHAR fields as NULLs. :-) Regards, Manuel Lemos