On 5/29/07, David Smith <[EMAIL PROTECTED]> wrote: > There was one point you made that I believe is inaccurate and so did not > include it in the above. Where you said that if you want to use the > convert_unicode option, you must know what encoding the database is in, but > my tests don't suggest that.
Oh, you're right. SQLAlchemy checks the character set of the connection. I thought of that after I sent my email. 2007-05-31 14:11:35,356 INFO sqlalchemy.engine.base.Engine.0x..8c show variables like 'character_set_results' > 1) The MySQL specific option of use_unicode is not needed anymore. The MySQL > specific charset option also is deprecated. I suppose. I'm still holding on to use_unicode for now though. The important thing is to use either convert_unicode or use_unicode. The MySQL charset option wouldn't work for me at all; it didn't recognize "utf8" as a valid choice. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
