It's been about two weeks since we released our CTP2 for the SQLSRV and PDO_SQLSRV drivers. While we've been actively monitoring and responding to feedback on our blog/forums, we have also been busy with the last set of "mini features" to complete our CTP2 release.
The “mini features” are limited to our installer for our Web Platform Installer (WPI) release. While our MSDN Download Center release is based on simpler IExpress technology (simple file uncompress and copy), the WPI installer is based on the Windows Installer technology – a requirement for WPI. Since WPI installs the VC6 Non-Thread Safe (NTS) version of PHP 5.2.13, our WPI release installer only installs the appropriate SQLSRV/PDO_SQLSRV drivers and, since the location of the PHP install is known, edits the php.ini file to enable the SQL Server drivers. This makes installation via WPI extremely easy even for novices.
The enhanced installer now includes two important features leveraging the capabilities offered by the Windows Installer infrastructure.
Now that we have completed these features for our installer, we have published our CTP2 binaries in WPI. At this time, the PHP applications supporting SQL Server published in WPI have not been updated to link to our CTP2 binaries, so one will have to install CTP2 manually after the application is installed.
So how does one install our CTP2 in WPI? Simple. Just download/install/run WPI, select the Web Platform tab, click the Customize link in the Database section, and check off Microsoft SQL Server Driver for PHP 2.0 CTP2, then click the Install button.
Regarding the CTP2 drivers themselves, we have received positive feedback on CTP2 with only a few issues reported to date. While we continue to address these issues, the good news is that these issues were not introduced by our code re-architecture or design changes in CTP2. In addition, we have received positive responses to our design changes in PDO_SQLSRV driver. While this is certainly good news, we continue to actively monitor the forums and investigate issues reported.
We are working thru the last set of bugs and expect closure on them soon. So, this is the right time for all to download and install our CTP2 driver immediately, hammer away at them, and report failures/regressions on our forum.
There is no VC9 support in 5.2. The WPI uses the php.net binaries which are built using VC6.
Thanks for the updates btw :)
I'm glad to see that PDO support will be added in 2.0 but I would also like to see an attribute that allows date fields to be returned as strings and not as DateObjects. This will make things easier when converting from another database that returns date columns as strings.
The attribue could be called PDO::ATTR_STRINGIFY_DATE_FETCHES or PDO::ATTR_DATE_STRING
I think the PDO extension *does* return dates as strings. This is from the documentation: "When using the PDO extension, dates are returned as strings. PDO has no datetime type."
Is it having the option that is most important to you, or actually getting dates as strings?
Brian is correct. We do note this in our documentation for ReturnDatesAsStrings connection option.
While the SQLSRV driver defaults to DateTime objects and provides the developer the option to receive them as strings using the ReturnDatesAsStrings connection option, we are responding to the feedback received for the PDO_SQLSRV driver to default to strings for datetime.
As we've said in a previous response to your comment of keeping with the "traditional PDO design", we did our best to work within the guidelines, intent and prevailing precedents. By returning datetime as strings by default, we feel we've achieved the goal of meeting the needs without extending PDO with a custom driver attribute.
Question is: do you want/need them to be returned as objects by our PDO_SQLSRV driver?
We are NOT changing the default for the SQLSRV driver as this is a breaking change for those that depend on this default.
I'm glad to hear that the PDO driver defaults to string for date/time columns.
Keep up the good work.