also, what im considering doing, is having assert_unicode only be  
implicitly turned on for the Unicode type specifically.   the engine- 
wide convert_unicode and String convert_unicode would not implicitly  
set the assert_unicode flag.  in this case you get the inconsistent  
round trips.



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.
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to