On 4/27/06, Baruch <[EMAIL PROTECTED]> wrote: > 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.
This is just conjecture, but on most Python distributions, the internal representation for a u"foo" is UTF-8, so that's probably why SQLObject defaults to it. I'm guessing that if you use the default UTF-8 encoding for a column and pass a Python Unicode string in a select, the comparison will work; if the SQLObject encoding is different from the internal Python encoding, it won't. Sounds like an important unit test to write, though. -- Tim Lesher <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
