Received: from koza.acecape.com (koza2.acecape.com [66.9.36.222]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0MEABl43752 for ; Tue, 22 Jan 2002 09:10:11 -0500 (EST) (envelope-from lists@natserv.com) Received: from p65-147.acedsl.com (p65-147.acedsl.com [66.114.65.147]) by koza.acecape.com (8.10.1/8.9.3) with ESMTP id g0MEA6d10692; Tue, 22 Jan 2002 09:10:06 -0500 (EST) Date: Tue, 22 Jan 2002 09:12:37 -0500 (EST) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: Christopher Kings-Lynne cc: Manuel Lemos , Francisco Reyes , PostgresSQL PHP list Subject: Re: PHP Abstraction layers In-Reply-To: Message-ID: <20020122091104.J42284-100000@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200201/43 X-Sequence-Number: 849 On Tue, 22 Jan 2002, 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 > > *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) > Chris 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.