note 55491 rejected from ref.pdo by dbs
| From: | dbs@php.net | Date: | Tue, 30 Aug 2005 23:44:10 +0000 |
| Subject: | note 55491 rejected from ref.pdo by dbs | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-94455@lists.php.net to get a copy of this message | ||
Note Submitter: taylorbarstow, at google's mail thingy
----
It seems like what would be REALLY useful, rather than another db abstraction layer like Pear::DB (I
know, the developers say this isn't an abstraction layer like Pear::DB, but look at the
interfaces! They're very similar) would be a generic data access interface that involves NO
SQL. Then, you could be really flexible about storage. PDO still allows lazy/ignorant developers
to put engine-specific SQL (like MySQL specific functions) into their queries. Data access objects,
on the other hand, allow ultimate portability and flexibility.
If you are unfamiliar with data access objects, see this intro:
http://www.onlamp.com/pub/a/php/2004/08/05/dataobjects.html
That's just a basic intro. Consider the power of creating a generic interface for data access.
Struts has had this for a long time, and IMO it's one of the major advantages that Struts has
over PHP.
Of course, creating a generic data access interface that involves no SQL is not easy. But there are
some pretty smart (pretty smart? I mean genius) developers around here. This is what open source is
for -- tackling the really tough problems!