Conversation
Notices
-
about a year ago from web
-
I've started using mysql-proxy and it wasn't handling non-latin character sets right. I think it's fixed now, though.
-
Was that an issue with php and solaris locales?
-
No. It was that the servers had latin1 as the default; our code uses 'SET NAMES "utf8"' on connect, but mysql-proxy doesn't pass thru to ro
-
...read-only servers when it's load-balancing. @jacques
-
I fixed the problem (I think) by setting utf8 as the default char set for all the servers.
-
Typically you ensure the following is set under the [mysqld] section in your /opt/local/etc/my.cnf: default-character-set=utf8
-
default-collation=utf8_general_ci character-set-server=utf8 collation-server=utf8_general_ci init-connect='SET NAMES utf8'
-
Apologies that this is posted over two replies. mysql proxy transparently redir q's so that the new connection is not aware of the charset.
-