Well I've fixed the problem on both the password field and the name field. It turns out that I had to set the mxODBC connection to use the latin-1 encoding and force it to use unicode strings. Once I did that, I got no more errors.
Looking at the data that was being used in the INSERT statement, the strings now start with a 'u' to indicate unicode (but were otherwise unchanged), and I have no more issues. I'm wondering if forcing the ODBC connection to go to unicode for everything would cause any problems down the road. Is there a _better way_ to handle this sort of encoding mess? Thanks, Brian Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
