Let's try this one more time, just in case it got scimmed over :)
Hello everyone.
I'm hoping the developer of MyODBC hangs out on this list, but here goes. I
browsed through the sources a bit, and I noticed several places where you
are mapping SQL_BIT type to TinyINT. It appears this is only a one way
mapping (software->odbc->mysql) and not the other way.
What I would like is 1 of 2 things, either
1) A possible update to MyODBC where an option can be checked (similiar to
large results etc..) that allows TinyINT columns to be "converted" to
SQL_BIT when sent to the software or
2) Pointers on where in the sources the "translation" is done when coming
from mysql.
Reason I need these is I'm under the gun to "fully" integrate Visual FoxPro
with MySQL (one data source, that whole thing) and the current Visual FoxPro
tables use a LOT of bool fields. So if I can do a little translation on the
fly, I can fake this, and make everyone happy :)
Thanks in advance,
Eric Fitzgerald
Server Administrator
AMN Television Marketing
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
