Differences in VC6 and VC9 Windows builds and MSSQL Driver. View as Markdown

2008/12/31 Richard Quadling rquadling@googlemail.com:

With Microsoft having their own PHP extension for talking to MSSQL
(http://www.microsoft.com/sqlserver/2005/en/us/PHP-Driver.aspx -
though documented to only support SQL 2005 and 2008, not 7 or 2000),
could this become the standard alternative for php_mssql.dll (though
not PDO as the MS extension is procedural only, leaving ODBC as the
route for older versions?

http://www.codeplex.com/SQL2K5PHP is another link for this extension.

Regards,

Richard.

Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

Hi Richard,

I am not sure, if VC6 can be dropped easily. E.g. some SAPIs that directly
map into servers may have problems if using the wrong CRT. Until now, I had
no time to build up a Windows "Sun Java System Webserver" and test it with
both CRTs. The code compiles fine on the snaps box, but I am not sure, if
the DLL loads into the server.

To the snaps build: The NSAPI module tests for "#define ZTS" and does
therefore not compile without thread safety. Why do the windows non-ts
builds on snaps.php compile? Is ZTS on windows always defined (it looks like
so in the makefile). How to test on windows, if thread safety is available?
But better would be to disable thread-unsafe builds for the NSAPI SAPI from
the beginning.

Uwe

Uwe Schindler
thetaphi@php.net - http://www.php.net
NSAPI SAPI developer
Bremen, Germany

-----Original Message-----
From: Richard Quadling [mailto:rquadling@googlemail.com]
Sent: Wednesday, December 31, 2008 11:12 AM
To: PHP Documentation ML; PHP Developers Mailing List
Subject: [PHP-DEV] Differences in VC6 and VC9 Windows builds and MSSQL
Driver.

Hi.

With regard to http://bugs.php.net/bug.php?id=46971, how much effort
is needed (if any) to document that some functionality is not going to
be available in all windows builds? [DOC]

Or,

When will VC6 be dropped? [CORE and DOC]

Admittedly, it is only an issue for Microsoft SQL Server (mssql and
pdo_mssql) and for Sybase_ct.

With Microsoft having their own PHP extension for talking to MSSQL
(http://www.microsoft.com/sqlserver/2005/en/us/PHP-Driver.aspx -
though documented to only support SQL 2005 and 2008, not 7 or 2000),
could this become the standard alternative for php_mssql.dll (though
not PDO as the MS extension is procedural only, leaving ODBC as the
route for older versions?

--

Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

hi Richard,

On Wed, Dec 31, 2008 at 11:11 AM, Richard Quadling
rquadling@googlemail.com wrote:

Hi.

With regard to http://bugs.php.net/bug.php?id=46971,

Can you repost (and subscribe to the list if you did not subscribe
yet) to the right list please (Windows Internals list)?

Thanks,

Pierre

http://blog.thepimp.net | http://www.libgd.org

With Microsoft having their own PHP extension for talking to MSSQL
(http://www.microsoft.com/sqlserver/2005/en/us/PHP-Driver.aspx -
though documented to only support SQL 2005 and 2008, not 7 or 2000),
could this become the standard alternative for php_mssql.dll (though
not PDO as the MS extension is procedural only, leaving ODBC as the
route for older versions?

I do not see us adding a new RDBMS specific extension that only works
on one OS (that is not even our main target OS in practice for
deployment) for an RDBMS that is also quite a niche solution for PHP.
Actually the only RDBMS where I am willing to currently consider a new
non PDO extension sqlite.

As such I do not think we should consider bundling this extension, let
alone have it replace the php_mssql.dll.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org