So it's not just a trick of my mind or my configuration it is indeed in MySQL.
I'll stick to my current solution of using StringCol and overriding the _set and _get methods to do the unicode conversion. Maybe I should create a MyUnicodeCol() that uses 'ignore' when decoding rather than the current 'strict' method that generates those exceptions. I do wonder how PostgreSQL handles this case? Does it not truncate the string, or does it truncate it smartly? Baruch --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
