Re: Re: Couldn't find your reference

EM>> Though I don't think that opinions from Slashdot should dictate the EM>> development decisions of PHP, they second the feeling I already got EM>> from customers. It seems that the most annoying thing for users of EM>> PHP (not students or freaks who use it at home and who didn't ever EM>> see a real commercial database, but corporate users) is the lack of EM>> such an interface. I personally don't see why this should be taken to the PHP core. Wouldn't it be better to make some "libc" (or "libdb" or "stdlib") for PHP, make it easily installable and multi-user (which PHPLib isn't) - maybe via model similiar to DBI approach, and take it to the PHP distribution? I do not think it's impossible, and I do not think that everything and a kitchen sink should be inside the language per se. Moreover, external model can be made much more elegant, much more clean from the OO point and certainly much more cutomizable and extendable. The trade-off will be a slight decrease of speed, but you can always fall back to the fastdb_native_query... To sum up: I think there should be some "standard classes" set for PHP, that certainly should include DB abstraction layer. Along with some other very useful classes (like templates, user management, authorization management, etc). But this should be external class library. Anyway, many languages get along with "keep all function in libraries" approach pretty well. -- Stanislav Malyshev Zend Technologies Ltd. stas@zend.com http://www.zend.com/ 050-624945