pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Manuel Lemos <mlemos@acm.org>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Francisco Reyes <lists@natserv.com>
Cc: PostgresSQL PHP list <pgsql-php@postgresql.org>
Subject: Re: "SQL" REPLACE SYNTAX
Date: Wed, 23 Jan 2002 03:54:27 -0200
Message-ID: <3C4E5013.CA5C24FC@acm.org> (raw)
References: <GNELIHDDFBOCMGBFGEFOKECICBAA.chriskl@familyhealth.com.au>

Hello,

Christopher Kings-Lynne wrote:
> 
> > Look at Metabase implementation. Metabase comes with a driver
> > conformance test that verifies if features like this work properly in
> > all supported databases. Don't you think that I would release a version
> > of Metabase that would not pass that test if all databases?
> >
> > The application needs to hint it as it is something that does not change
> > at runtime, so there is no penalty of figuring that by querying the
> > database server and some database do not provide a way to tell you which
> > fields are the primary key.
> 
> OK, so it's not a simulation of the MySQL syntax - MySQL requires no hints.

No, but the functionality is the same. MySQL ignores the hints because
SQL REPLACE works as intended without the hints.



> I've looked thru the code and yeah, basically that's what you have to do, so
> long as you can get the app programmer to tell you in the code what the
> primary keys are.  For a postgres implementation, it's more difficult.

It is required. If the programmer does not tell which fields are the
keys, the function will fail with an error stating that.


 
> BTW, there's no documentation anywhere in your code - makes it a bit
> difficult to see what's going on...

Erm.... there is 248K HTML document that details all about that function
the whole Metabase API. :-)

Regards,
Manuel Lemos



view thread (15+ messages)  latest in thread

Message-ID: <3C4E5013.CA5C24FC@acm.org>
Permalink:  ../3C4E5013.CA5C24FC@acm.org/
Also on:    postgresql.org/message-id/3C4E5013.CA5C24FC@acm.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: mlemos@acm.org, chriskl@familyhealth.com.au, lists@natserv.com
  Subject: Re: "SQL" REPLACE SYNTAX
  In-Reply-To: <3C4E5013.CA5C24FC@acm.org>
  References: <GNELIHDDFBOCMGBFGEFOKECICBAA.chriskl@familyhealth.com.au> <3C4E5013.CA5C24FC@acm.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox