On Nov 27, 2007, at 2:36 PM, Rick Morrison wrote:
> What's the point of the new 'assert_unicode' flag? It's causing > failures with pymssql DDL (in my case CREATE / DROP) > > Is there a good reason to not only allow unicode, but to *enforce* > it for DDL? > > I'd like to have one set of tabledefs, prefererably in ASCII for DB > portability. > the assert_unicode thing only happens with python SQL expressions, usually DDL is issued using textual SQL. if youre using a SQL expression for your DDL, just put assert_unicode=False in the String objects youre using. the point of the flag, like i mentioned on devel, is so that people know that they should be using unicode and not str objects if they are dealing with a unicode application. otherwise you get invalid round trips: table.insert().execute(foo = 'bar'), then table.select().scalar() == u'bar'. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
