i18n support in MySQL DB and MySQL client applications
Posted by: Hemant Ramnani
Date: August 03, 2005 07:20PM

Hi All,
I wanted to have an opinion on the following, is it a good practice to have the following options set in
the MySQL DB side (my.cnf file) when I am writing i18n applications and handle UTF8 data on the client side applications:

[mysqld]
init_connect='SET collation_connection = utf8_general_ci'
init_connect='SET NAMES utf8'
default-character-set=utf8
character-set-server = utf8
collation-server = utf8_general_ci

[mysql]
default-character-set=utf8

OR

DO NOT have the above settings in the "my.cnf" file, create databases everytime with a particular/specified character encoding and then have every client of the DB act accordingly.

I personally feel the former option is the way to go when writing i18n enabled applications against MySQL DB.

Comments would really be appreciated.

Thanks,
Hemant R.

Options: ReplyQuote


Subject
Views
Written By
Posted
i18n support in MySQL DB and MySQL client applications
4216
August 03, 2005 07:20PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.