On 2/21/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > I don't think a problem with the program is in unicode itself. I suspect > the problem is in "unicode-insisting" version of MySQLdb. There have to be > a proper charset/encoding set, and there have to be a proper handling of > them in SQLObject's MySQLConnection (and I am not sure how good that is, > though there is a constant stream of patches from MySQL users...)
Agreed, with MySQL you'll definitely need to use the sqlobject_encoding parameter in the datbase connection URI. I'm currently using non-ASCII characters and UnicodeString columns without problems on MySQL 5 with a connection string like: mysql://user:[EMAIL PROTECTED]/dbname/?sqlobject_encoding=latin1 I've gotten the impression that with MySQL 4 one is unlikely to have much luck (haven't tested it myself). Schiavo Simon ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
