On Sat, Jul 3, 2010 at 1:07 PM, Pierre Joye <pierre....@gmail.com> wrote: > hi, > > On Sat, Jul 3, 2010 at 8:40 PM, Stanley Sufficool <ssuffic...@gmail.com> > wrote: > >> I would argue that the additional fixes in trunk fix bugs rather than >> introducing new functionality since they were already in the PDO >> specification and they do not break BC. I do not see why this would be >> held out of releases. > > They should, only not right now in 5.3.3/5.2.14 as we are in the > second release candidates. The reasons why we should not begin to > apply dozen of patches at this stage are rather obvious, hopefully :). >
Got it. Thanks. > >> FWIW, Microsoft has a monopoly on a fully functional PDO mssql driver >> which is only implemented on MS platforms. If we want portability of >> PHP applications, then the PDO DBLIB driver must be fully functional >> on releases. > > That's not correct. PHP 5.3+ has no SqlServer support on Windows. The > SqlSrv driver is more than welcome as it solves this problem. The PDO > support is still beta (CTP2). However all other platforms do have > SqlServer support by default in the core. Sorry, I was incorrect, the Microsoft PDO SqlServer is still in release candidate stages. I'm just hoping to have an on-par PDO implementation available on all platforms before everyone starts coding for the platform dependent driver. > >> BTW, This extension is experimental and subject to change. Well it >> did, and they were warned. > > Hence the worries? :) I am saying that this extension on the PHP doc pages is marked as experimental and as such the users should not expect the behavior to stay consistent. But none-the-less, the patches do not affect any _existing_ behavior. So no worries. :) > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
