RE: [PHP] Database Code Portability
| From: | Dallas Kropka | Date: | Sat, 17 Feb 2001 07:19:19 +0000 |
| Subject: | RE: [PHP] Database Code Portability | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-40301@lists.php.net to get a copy of this message | ||
Try taking a look at the ADODB class written by the people at
www.phpeverywhere.com (net?) We are using this code. it supports all major
functions of 9 different databases.... and is very solid.
-----Original Message-----
From: Dave Haggerty [mailto:haggerty@ix.netcom.com]
Sent: Friday, February 16, 2001 10:55 PM
To: php-general@lists.php.net
Subject: [PHP] Database Code Portability
I haven't seen this issue discussed, sorry if I missed it:
My question is why are the PHP database functions so unportable? Is there a
reason why they have to be specific to, say MySQL. It seems to me (even
though I am an amatuer to this stuff) that the code should be much more
easily portable from one db to another?
Do most coders add an abstraction layer themselves? Or maybe people just
don't port PHP code much and so don't worry about it?
Mainly curious....
Dave
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
For additional commands, e-mail: php-general-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net