Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase
| From: | Alexander Merz | Date: | Wed, 21 Nov 2001 18:28:09 +0000 |
| Subject: | Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3032@lists.php.net to get a copy of this message | ||
> I think, the problem is here, and what can do pear-developers with difference
> in SQL for DBMS? IMO, nothing, exept only ask DBMS-developers to follow the
> sQL92 standatd..:)
100% Agree
We have to differ between two types of abstraction layers:
- an unified database layer
- an unified SQL layer
PEAR::DB is the first kind of layer. It's not your beer, when a programmer use
DB specific statments. It unifieds the API and provides independence from the
specific db API.
The second kind of layer has to provide function like select(), update() ...
they can base on the db layer and provides independence from SQL.