From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Manuel Lemos" <mlemos(at)acm(dot)org> |
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 05:41:25 |
Message-ID: | GNELIHDDFBOCMGBFGEFOKECICBAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
> 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.
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.
BTW, there's no documentation anywhere in your code - makes it a bit
difficult to see what's going on...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Lemos | 2002-01-23 05:54:27 | Re: "SQL" REPLACE SYNTAX |
Previous Message | Manuel Lemos | 2002-01-23 05:26:14 | Re: "SQL" REPLACE SYNTAX |