Re: [PDO] PDO transaction isolation level and firebird

--------------060803090807080905050108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello

Working with a code base that is older then 10 years and was first based 
on PHP4 then PHP5, it used PEAR DB & MDB2 and since some time PDO.

I have to say PDO is still good enough for most basic tasks, but most in 
it isn't pretty. My connection routine for mysql pdo needs some tweaks 
here and there from time to time. On the other hand the main usage and 
code related to Database usage doesn't change much since PDO. I guess 
using mysqli with mysqlnd will trigger some edge cases as well.

I am not sure about Zend_DB argument here, it provides some kind of PDO 
compatible access layer for mysqli. So I don't worry much Database 
connection these days, most stuff is hidden between some layers of glue 
code. (Some lightweight glue code and some heavy framework usage for 
other projects). As so many projects use PDO like abstraction layers in 
some form it's likely to stay, or you should be able to replace PDO with 
Zend_DB or any other emulation/layer/glue code.

I wish there would be some PDO improvements. It is even less likely that 
PDO get enough maintainers as there are so many new databases using some 
kind of document access.

Considering pdo_mysql has a ton of special constants I can't understand 
why pdo_firebird shouldn't get special attributes for isolation level 
when proper documented.  The overall PDO should unify all database 
access is already broken at binding level.

Since ages PHP is a moving target, for me this means that the develop 
environment is one major version ahead and mostly that worked good 
enough.  Switching PHP version for the Netbeans project should help to 
spot some problems as well.

Best regards
Oskar Eisemuth

--------------060803090807080905050108--