Bug #38991 Cannot read bit fields with ODBC Connector 5.1 - all True
Submitted: 24 Aug 2008 10:15 Modified: 24 Aug 2008 18:17
Reporter: David Webb Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:5.1.5 OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: Bit field, cannot read, ODBC Connector

[24 Aug 2008 10:15] David Webb
Description:
Cannot read bit(1) values in Microsoft Access 2003 linked table connecting to MySQL through ODBC Connector 5.1.5. The bit fields all show "true" values when in fact I know they are a mixture. The server and the client are on the same machine, Windows XP SP3.

It works fine with connector 3.51.26, so this was probably introduced in 5.1.x

How to repeat:
Set up a table in MySQL with Bit(1) fields, populate it with random 1 and 0, then link to it from MS Access 2003 and look at the table.

Suggested fix:
I have no idea. I downgraded to 3.51.26 and that works fine.
[24 Aug 2008 18:04] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #36470
[24 Aug 2008 18:17] David Webb
I did do a search before submitting, and I don't think it's the same bug. The other bug report talks about problems after update via a View, but the report I submitted is not about any update problem and does not involve a view. Simply opening the linked table in access produces value TRUE for all bit fields. I am linking directly to a table, not to a view of that table.

Anyway, if you kill two bugs with one stone then that's great.