ID:               26820
 Updated by:       [EMAIL PROTECTED]
 Reported By:      subspace at wanadoo dot nl
-Status:           Assigned
+Status:           Closed
 Bug Type:         MSSQL related
 Operating System: Debian Linux 2.4.21
 PHP Version:      4CVS-2004-02-06
 Assigned To:      fmk
 New Comment:

This problem has been fixed in FreeTDS. Works on both Windows and
Linux.


Previous Comments:
------------------------------------------------------------------------

[2004-10-18 20:39:06] freddyz77 at tin dot it

dblib use by default TDS protocol 4.2. This protocol do not support
null bits so it return 0 instead. Use protocol 7.0 or more (8.0 for
mssql2k). This can be configured using FreeTDS (but not using MS
dblib).

------------------------------------------------------------------------

[2004-02-25 14:53:26] [EMAIL PROTECTED]

On Win32 this is caused by a bug in dblib (the Microsoft library used
to build the extension).

------------------------------------------------------------------------

[2004-02-21 05:45:07] egarcia at egm dot as

I have the same problem in Windows XP, Windows 2000, using MSSQL 2000.

I call a store procedure that returns data using rollup over a bit
field.  In the sumarized data MSSQL return NULL in the bit field but
PHP give me a zero (0).

The expected result is to get the NULL value data.

The example in the posted message is TOTALLY replicable in my system.

------------------------------------------------------------------------

[2004-02-06 13:44:31] subspace at wanadoo dot nl

./configure --with-mssql --without-mysql
The mysql option is irrelevant though. 
FreeTDS package installed: freetds-dev    0.61-5

X-Powered-By: PHP/4.3.5RC2

bit: int(0)      tiny: int(0)
bit: int(1)      tiny: int(1)
bit: int(0)      tiny: NULL

------------------------------------------------------------------------

[2004-02-06 11:35:33] [EMAIL PROTECTED]

One more information is needed: what was the configure line used to
configure PHP?


------------------------------------------------------------------------

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
    http://bugs.php.net/26820

-- 
Edit this bug report at http://bugs.php.net/?id=26820&edit=1

Reply via email to