Bug #13176 BIT Fields doesn't translate to Logical under Foxpro
Submitted: 14 Sep 2005 11:36 Modified: 7 Sep 2007 14:22
Reporter: Philippe Mingo Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S4 (Feature request)
Version:3.51 OS:Any
Assigned to: CPU Architecture:Any

[14 Sep 2005 11:36] Philippe Mingo
Description:
When using VisualFoxpro, MS SQL server ODBC translates BIT fields to
logical values (.t. and .F.). While MySQL translates to a numeric value.
It would be nice that they translate both the same way. Porting from MS
SQL Server to MySQL would be easier.

How to repeat:
Obtaining a Bit Field from VisualFoxpro and looking at the type should be enough ;)
[7 Sep 2007 13:14] Susanne Ebrecht
Hi Philippe,

this is not a MySQL problem. The data type BIT is defined in MySQL as:

"A bit-field type. M indicates the number of bits per value, from 1 to 64. The default is 1 if M is omitted."

MS SQL makes it's own definition for BIT.

If you want to get back true or false, please use the data type boolean.

Regards,

Susanne
[7 Sep 2007 14:05] Tonci Grgin
Hi Philippe. This is not a bug but expected behavior as Susanne already explained.

Thanks for your interest in MySQL.
[7 Sep 2007 14:22] Philippe Mingo
wow! This was a two years old post !!! XD

I already workarounded the problem, but thanks anyway ;)
[7 Sep 2007 14:49] Tonci Grgin
Phillipe, I am truly sorry for the delay. This report was posted even before I joined. But, if you have noticed, recently we have staffed MyODBC team and there is even time to look through old reports and help where possible.

Thanks for your interest in MySQL!