Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase
| From: | Teodor Cimpoesu | Date: | Thu, 22 Nov 2001 09:52:03 +0000 |
| Subject: | Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3038@lists.php.net to get a copy of this message | ||
Hi Paul!
On Wed, 21 Nov 2001, Paul Meagher wrote:
> Manual Lemos Wrote:
> > If you want to resort to non-portable database programming, just stick
> > with the native database API that PHP offers and you will get all the
> > speed that is possible. Using a database abstraction that does not offer
> > portability and still adds execution overhead does not make much sense.
> > Your programs still need to be adapted to run with different databases
> > and they will still be slower than using the native PHP database APIs.
>
[snip]
> It may be true that PHP only has one true DB Abstraction layer and that is
> Metabase. If that is the case, then I think we should not call PEAR DB a
> database abstraction layer if it confuses this important distinction. A
> Unified API is probably a more accurate term as was suggested before.
>
you mean something like Unified ODBC which uses native calls for a series of
databases?
my $euro = .2; :)
-- teodor