Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase
| From: | Alexander Merz | Date: | Wed, 21 Nov 2001 14:47:07 +0000 |
| Subject: | Re: Re: Common DB Abstraction Layer: Re: [PEAR-DEV] Adoption of Metabase | ||
| References: | 1 | Groups: | php.db php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3023@lists.php.net to get a copy of this message | ||
>Now for the $15,000 question: does anyone else agree with this ? If
>PEAR::DB is not abstracting the database what is the purpose of such a
>library ?
a) unifed API
You havn't to think about the name of the command to send a query,
connecting...
b) it offers helpful functionality
I.e. don't care about quoting and escaping in SQL-Statments, the query command
does it for you. PEAR:DB contains different possibilties to access the result
set... (Yes you can write such functions too, but why recreate the wheel?)
c) _helps_ to keep portability
You have 'only' to change the SQL-statments, not the functions.