Raja Subramanian wrote:
On Fri, Dec 26, 2008 at 12:02 PM, Vamsee Kanakala <[email protected]> wrote:
I'm not so sure. PHP is not exactly a general purpose language. It's meant
for writing web apps. And db-driven ones at that. They are bound to get big
sooner or later. Not providing for re-use and maintainability is a fairly
big omission, imho.

+1

I would image a typical use case for php is to connect to a backend
DB and generate html.  In this situation, I can't understand why a DB
abstraction layer is also not a part of the standard libraries.

I can't get why mysql_*(), mysqli_(), pg_*(), etc still exist when we
have adodb, peardb, etc.

Pretty much all the languages have db specific interfaces. I know atlteast, two reasons:

* Can't abstract away everything. The are many db specific unique features you might want to take advantage of.

* Compatibility. Nobody wants to keep rewriting the same code over and over again.

Rahul
_______________________________________________
To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc

Reply via email to