Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase
| From: | Manuel Lemos | Date: | Tue, 27 Nov 2001 22:02:39 +0000 |
| Subject: | Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.dev php.pear.dev |
| Request: | Send a blank email to php-dev+get-71871@lists.php.net to get a copy of this message | ||
Hello,
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.
>
> I don't think portability in database programming is as categorical as you
> suggest. The fact that you have gone for 100% portability may be what
> makes you put other abstraction layers into the non-portable camp. The
You can do non-portable programming with Metabase if you want.
Portability is achived with additional that Metabase has unlike other
abstraction layers. You really need to know Metabase better.
Regards,
Manuel Lemos