Re: Re: Please test PDO

Hi everyone, long time no post! Wow, a lot has happened to PDO while I was looking the other way for a minute. I hope I will soon find the time to bring PDO_FIREBIRD up to date with all the recent changes. What would be a reasonable deadline for this (in relation to 5.1) ? Lester Caine wrote:

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.

As I've said before in our discussions about PDO, I am not very happy about the apparent 'impedance mismatch' between Firebird and PDO. If PDO is turning out to be a least-common-denominator solution like most abstraction layers, it's going to be impossible to ever provide the features that the original Firebird/Interbase driver does. For instance (these issues have been pointed out by me before): - Firebird has transactions over multiple connections [no JOINs between databases, but atomicity/consistency across multiple DBs]. There's no way this will ever be supported in PDO due to the way it was designed; - running concurrent transactions off the same connection; - named results; - the whole service API (inquiries about the server/database/users etc.); - event handling; So if the intention is to ultimately replace the Firebird/Interbase driver with a PDO one, a lot of work has to be done. And PDO *will* have to be changed to allow for the more exotic features of Firebird. -- Ard