On Aug 29, 2008, at 10:53 AM, Mike wrote:
> > If I use pymssql instead, it works. As I understand it, SA should be > using pymssql anyway, so I don't know why this is happening. I can > cast the unicode to a string, so it's not a big deal. However, I > thought someone might want to know that this is happening. without a sample of the code and schema in use, we can't say for sure what the issue is. Are you making usage of the Unicode type at least ? > > > Oh, and I use autoload to load my Table() objects. I'm not sure if > that's significant or not though. I am also using a session.commit() > to get the error above. You might want to enable convert_unicode=True on your Engine, or override the specific columns requiring unicode compatibility with the Unicode type. String columns are reflected by default without unicode awareness. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
