Hi, the proper way is to handle character encoding yourself, and pass unicode objects to methods that expect them.
When you get this SAWarning, you've just passed in a byte sequence (str in python 2.x) where a unicode object was expected. Your byte sequence *may* be an ASCII-encoded string but may (perhaps later on in your application's lifetime) be a differently-encoded string (or even not a string). Your application should know which encoding to apply (SQLAlchemy can't know), and apply it (e.g. with s.decode(encoding) where encoding might be 'utf8' or 'iso-8859-1' or 'utf16') before passing to SQLAlchemy. Regards, - Gulli -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
