Edit report at https://bugs.php.net/bug.php?id=48539&edit=1
ID: 48539
Updated by: ssuffic...@php.net
Reported by: frase at cs dot wisc dot edu
Summary: pdo_dblib fails to connect, throws empty
PDOException "SQLSTATE[] (null)"
Status: Closed
Type: Bug
Package: PDO related
Operating System: *
PHP Version: 5.2.10, 5.3.0RC4
Assigned To: felipe
Block user comment: N
Private report: N
New Comment:
I see that this option is not implemented in FreeTDS dblib.c. Calling DBSETOPT
with this option should have no effect and produce no error. Masking it for all
libraries except MS DBLIB (depreciated) is not a solution unless the underlying
FreeTDS library has a bug.
The previous implementation would return exit if DBSETOPT failed, causing the
connection to close with an error. The current version does not exit in error
if
the DBSETOPT returns FAIL.
Newer versions should return a more specific error than the "SQLSTATE[] (null)
(severity 0)". Please test again and provide the error if you can. I am running
Sybase ASE and so cannot accurately reproduce your error with MSSQL.
Previous Comments:
------------------------------------------------------------------------
[2013-09-25 14:55:58] kap...@php.net
The following patch has been added/updated:
Patch Name: mssql-null-exception
Revision: 1380120958
URL:
https://bugs.php.net/patch-display.php?bug=48539&patch=mssql-null-exception&revision=1380120958
------------------------------------------------------------------------
[2013-05-09 10:15:06] talktome at aboutandrew dot co dot uk
This problem exists in php 5.4.10
------------------------------------------------------------------------
[2012-12-13 16:08:25] wdmeldon at gmail dot com
I've tested this in 5.3.19 and was not able to replicate.
------------------------------------------------------------------------
[2012-07-13 13:10:20] snowcorenet at gmail dot com
Could anyone tell me, please, if this is fixed in php 5.3?
------------------------------------------------------------------------
[2011-04-11 18:37:18] tom at punkave dot com
Did this fix ever get put in PHP 5.3? I am getting this error exactly as
originally described with all PHP 5.3.x versions tried.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=48539
--
Edit this bug report at https://bugs.php.net/bug.php?id=48539&edit=1
