For some reason my new FreeBSD box using either 1.2.1_p1 or 1.2.2b1 both return char() fields as a python set. Accessing the same database from a linux box returns a string. VARCHAR() is returned as a string. Switching to unicode returns a unicode string for both CHAR() and VARCHAR() but not a set.
Any idea what's going on?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For some reason my new FreeBSD box using either 1.2.1_p1 or 1.2.2b1 both return char() fields as a python set. Accessing the same database from a linux box returns a string. VARCHAR() is returned as a string. Switching to unicode returns a unicode string for both CHAR() and VARCHAR() but not a set.
Any idea what's going on?
Hello
I've got the same problem on a OpenBSD 4 box...
Changed to Varchar the char() field, and returned a string instead of a SET ....
Is it a bug or what ?
http://bugs.mysql.com/bug.php?id=17758
Have you tried one of the 1.2.2 betas? I'm pretty sure it has the fix.