On Jun 4, 2010, at 12:43 PM, King Simon-NFHD78 wrote: > > If you're more comfortable with a version that just doesn't call > _check_unicode_returns, or that catches the exception, either would be > fine with me. I just sent the first thing I tried that seemed to work. I > agree that silently converting CAST to nothing might mask other bugs, > and so probably isn't ideal. > > Which would be your preference then? Catching the exception, or not > calling the method in the first place? I'll make a patch for whichever > you prefer and test it next week.
doing the "cast" thing at least allows us to get an answer to the unicode question from mysql 3. If you can make a trac ticket targeted at 0.6.2 milestone we can get started. It just needs a test case in dialect/test_mysql (it would create a dialect, hardcode server version to 3.23, assert that compiling cast(foo) produces the expected string). I can do the test part. -- 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.
