> On 2/6/06, BJörn Lindqvist <[EMAIL PROTECTED]> wrote: > > I've ran into the same problem. It seems to me like SQLObject is not > > able to automatically figure out which encoding the mysql-database is > > using so it falls back on latin1. The MySQLdb module has the same > > problem and to fix it you have to set the arg use_unicode=True when > > you instantiate the connection. > > I found out that in mysql you can add init_connect='SET NAMES utf8' in > the [mysqld] section of your my.cnf file and that fixes the problem. > So maybe this is not a problem with SQLObject after all?
I submitted a patch to SQLObject to be able to specify this on per-connection basis, see http://sourceforge.net/tracker/index.php?func=detail&aid=1421263&group_id=74338&atid=540674. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
