Re: [PDO] PDO transaction isolation level and firebird

there is lot of work need to be done in pdo_firebird driver currently it is nearly unusable becouse of not accepted patches to bugs #60052 (negative int results returning incorrect, really hard to use driver with this bug), #63105 (read committed isolation level is only makes sense on big concurent databases), #64603 (unable to use peristent connects), #65689 (again unable to use persistent connects, memory leaks) ,#65690 (unable to use dialect 1, it is still alive) and futher work is stopped becouse new patches may conflict with old patches so i have question, what need to do to get patches to upstream? 2013/9/27 Vjacheslav V. Borisov <slavb18@gmail.com> > The re is no direct 1-to-1 match of ansi to firebird isolation levels > see http://www.devrace.com/en/fibplus/articles/479.php > So I deceided to make FB_ transaction isolation level constants > I can declare ISO isolation levels at PDO level > and match > (ISO) READ COMMITTED = (FIREBIRD) READ COMMITTED RECORD_VERSION > (ISO) SERIALIZABLE = (FIREBIRD) SNAPSHOT > but another isolation levels do not match > > > 2013/9/27 Matteo Beccati <php@beccati.com> > >> Hi, >> >> On 25/09/2013 06:53, Vjacheslav V. Borisov wrote: >> > Ok, I submitted patch to bug #63105 >> > https://bugs.php.net/bug.php?id=63105 >> >> database driver specific attributes are discouraged, unless they >> specifically apply to that driver only. Now, transaction isolation level >> seems to be quite a common feature that is described by the SQL >> standard... I'd be very reluctant to accept the patch as-is. >> >> >> Cheers >> -- >> Matteo Beccati >> >> Development & Consulting - http://www.beccati.com/ >> > >