#37671 [Opn]: MySQLi extension fails to recognize BIT colums

ID: 37671 Updated by: tony2001@php.net Reported By: squasar at eternalviper dot net Status: Open Bug Type: MySQLi related Operating System: * PHP Version: 5.2 CVS Assigned To: iliaa New Comment: With MySQL 5.0.21 & latest 5_2 CVS I get long(0)'s. Previous Comments: ------------------------------------------------------------------------ [2006-06-25 10:25:31] squasar at eternalviper dot net I updated to the latest 5.2 branch on CVS and run the exact test code I submitted again. The result: long(0) refcount(1) long(0) refcount(1) long(0) refcount(1) long(0) refcount(1) I don't know what one of us is doing wrong. Tested on both big-endian and little-endian systems. Could it be a 32-bit vs. 64-bit issue? ------------------------------------------------------------------------ [2006-06-20 20:54:29] iliaa@php.net With latest CVS your code returns the following results: long(1) refcount(1) long(0) refcount(1) long(1) refcount(1) long(0) refcount(1) ------------------------------------------------------------------------ [2006-06-08 06:27:06] squasar at eternalviper dot net That sample from the manual is irrelevant. Re-examine the reproduce code I provided. It FAILS using the patch that was applied to CVS; the result is always zero regardless of the values in the column, even though it's a BIT(1). ------------------------------------------------------------------------ [2006-06-07 13:08:32] iliaa@php.net BIT[(M)] A bit-field type. M indicates the number of bits per value, from 1 to 64. The default is 1 if M is omitted. (From MySQL manual) ------------------------------------------------------------------------ [2006-06-07 04:43:39] squasar at eternalviper dot net The patch applied to CVS does NOT fix the bug. The CVS patch folds BIT handling into LONG types. This does not work; BIT columns take a 64-bit type, NOT a 32-bit type. Please re- examine the patch I supplied, which folds BIT handling into LONGLONG types. ------------------------------------------------------------------------ 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/37671 -- Edit this bug report at http://bugs.php.net/?id=37671&edit=1