George Schlossnagle wrote:
PHP has long suffered from poor implementations of some of the DB extensions and good implementations of others. PDO is a good opportunity to unify the extensions and have a common code base so that bug fixes
Excuse my ignorance, maybe I missed the answer to Lester's question: What's the proposed way of accessing the DB-specific functionality once PDO is there? Is everything available through SQL statements or get/srcAttribute? After a first look at the MySQL functions my guess is that that's the case. At least I can't see anything I need which I couldn't reach that way.
Please enlighten me,
THAT is the nail I was missing. Firebird has a number of functions that are not managed via SQL, and require the 'services' interface.
That question has been answered at least twice in this thread, with specific examples given regarding mysql (or at least using mysql as the example).
PLEASE - I am trying to be as constructive as I can. Until the php_firebird driver code is brought up to date with the latest core code I can't get much of what IS available working, so I am looking to what functions still need the php_interbase driver running in parallel to see what can be done about them. What is needed fairly soon is a hook where we can document these engine specific details and perhaps give pointers as to how missing functionality can be got around. This will at least then provide an indication as to what still needs to be done on a driver by driver basis, and more important, somewhere we can look for hints when trying to carry out those same functions on other engines.
My previous messages were badly worded and were not explaining things very well. I got panicked again by the 'replacing existing drivers' comments which is still a concern given the work that is currently being done on changes to most of the database engines and in my case Firebird and I hope that these drivers are not simply side-tracked - until PDO *IS* in a position to provide the same functionality - which is still some way off yet? Maintaining backwards compatibility is all very well, but if you can't access the nice new stuff ....
I apologise if my attitude has annoyed but I am not in the slightest embarrassed ;) as I still think that lessons need to be learnt from the existing methods of doing things to provide an excellent generic solution. Us old timers get used to the crutches, so when someone takes them away we start drowning :)
-- Lester Caine ----------------------------- L.S.Caine Electronic Services
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
