On Thu, Sep 25, 2008 at 6:47 AM, Michael Bayer <[EMAIL PROTECTED]>wrote:
> Converting *all* strings to unicode would then lead to havoc as soon > as someone adds a Binary column to their schema. Another solution, > which we have support for, would be for ResultProxy to attempt to > match TypeEngine objects to the DBAPI types in cursor.description. > We already do this for Oracle binary types, so perhaps this > functionality could be enabled for all types. Its backwards > incompatible though so it would need to be a create_engine() option > (I'd call it "detect_result_types"). A technical issue with this > option is that it creates issues with table reflection which would > have to be worked around somehow. > The "?charset=utf8&use_unicode=1" parameter produces the expected behavior. I DID check the documentation and mailing list archives (many posts) before raising this issue but I thought use_unicode and convert_unicode were different forms of the same thing. I in fact DID try "?convert_unicode=1" as a URI paramater which of course was incorrecct. I'll try to write up a wiki page on Unicode. I'm assuming that the '?uri_params' are specific to each driver (ie mysqldb) so the syntax for unicode support may be different for each? I'm also planning on using binary strings so I need to write some more tests, although I THINK I understand what is going on now. Thanks again, Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
