Re: Database Code Portability

Hello Dave, On 17-Feb-01 01:52:57, you wrote: >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 Different databases provide different features through different API. >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? Yes, most people don't care much about writing database independent code, because they assume they will never need to switch from their current database of choice. This is often not the case. Many developers that started with lower end database like MySQL and PostgreSQL often realize that they need their databases to scale up to a point that you will need an high end database to handle. Other developers find themselves in the opposite migration way. They develop products that rely on specific high end databases but then they realize that there is a much wider audience of low end database users that could be interested in their products if they could work with those databases. This uncertainty of the future needs lead me to start developing Metabase two years ago. Metabase is a PHP database abstraction package that you may rely to write database independent applications. It features not only database independent access but also database independent schema installation. Metabase is free and you may want to look at it here: http://phpclasses.UpperDesign.com/browse.html/package/20 Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org -- E-mail: mlemos@acm.org URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp --