Mike,

Mike wrote:

....
>
> I found the issue. For some reason, SqlAlchemy is passing a unicode
> string to a varchar field in SQL Server, which is causing an error to
> be raised. If I explicitly set the value to an integer or a string, it
> works fine. I'm not sure how it's getting cast to unicode, but I think
> I can work around this.
>   
How is your model defined?  Maybe the column is incorrectly defined in 
the model or if you use autoload then maybe there is a problem with the 
autoload code.

I would also work around it, but provide some more details here in a new 
thread as it might point to a problem in SA.

Werner

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

Reply via email to