>> What I don't know is how to tell SQLObject (if at all possible) to use >> UTF-16 instead of UTF-8... > > I haven't used it myself, but UnicodeCol accepts a "dbEncoding" > parameter, which defaults to "UTF-8".
Seems like that should be the solution, looking at the source there is indeed a dbEncoding attribute to UnicodeCol and using UTF-16 will make more sense than UTF-8 for me. The data I have is always kept in Unicode inside my app anyway and I don't care much about non-Python code reading the data. I still feel that SQLObject is not doing the obvious thing here, it should use the UTF-16 encoding from the start especially when it has this comment for UnicodeCol: "Note: parameters in queries will not be automatically encoded, so if you do a query matching a UnicodeCol column you must apply the encoding yourself." This will bite the ass of anyone who naively uses UnicodeCol's and thinks that his queries will just work properly. I'm pretty sure the Identity system uses UnicodeCol throughout, did anyone really checked if they work for non-ascii characters? esepcially those cases where the unicode string is encoded into a too long username string? 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 -~----------~----~----~----~------~----~------~--~---
