RE: [PHP] Database Code Portability

A simple to it solution is PHP Library (PHPLIB) phplib.netuse.de, or the ADODB class which Dallas was referring to you. Using these not only makes a db more portable to you but it also easier to do connections and queries from your software. Sincerely, Maxim Maletsky Founder, Chief Developer PHPBeginner.com (Where PHP Begins) maxim@phpbeginner.com www.phpbeginner.com -----Original Message----- From: Dallas Kropka [mailto:dallask@austin.rr.com] Sent: Saturday, February 17, 2001 4:19 PM To: Dave Haggerty; php-general@lists.php.net Subject: RE: [PHP] Database Code Portability 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 -- 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