| From: | Francisco Reyes <lists(at)natserv(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Manuel Lemos <mlemos(at)acm(dot)org>, Francisco Reyes <lists(at)natserv(dot)com>, PostgresSQL PHP list <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: PHP Abstraction layers |
| Date: | 2002-01-22 14:12:37 |
| Message-ID: | 20020122091104.J42284-100000@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-01-22 15:52:45 | Re: Long running queries and timeouts |
| Previous Message | Manuel Lemos | 2002-01-22 05:01:31 | Re: PHP Abstraction layers |