| From: | Manuel Lemos <mlemos(at)acm(dot)org> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Francisco Reyes <lists(at)natserv(dot)com>, PostgresSQL PHP list <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: "SQL" REPLACE SYNTAX |
| Date: | 2002-01-23 04:39:22 |
| Message-ID: | 3C4E3E7A.A48929A4@acm.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-01-23 05:21:18 | Re: "SQL" REPLACE SYNTAX |
| Previous Message | Christopher Kings-Lynne | 2002-01-23 03:56:34 | Re: "SQL" REPLACE SYNTAX |