Are there any issues with MySQL's i18n(indic language) support?

We're evaluating MySQL and PostgreSQL for building our indic language(using utf-8 encoding) web application which will use MySQL or PostgreSQL.

One of my colleagues mentioned that MySQL had issues with i18n. I mostly come from the Oracle world and although I've played a lil with MySQL, I don't know enough to know that there are is开发者_开发知识库sues with its i18n support.

Does anyone know issues with MySQL's i18n support and if PostgreSQL would be better placed for building an application with indic language support(kannada, telugu, tamil, etc) using utf-8 encoding ?

Just so you know, we're going to be using J2EE to build this application and we will be using JDBC drivers to access the DB.

P.S : Will anything change if we were to use Rails to build the app instead of J2EE ?

Thank you,

MySQL doesn't support the complete utf8-encoding:

Currently, MySQL support for UTF-8 does not include four-byte sequences.

PostgreSQL has full support for utf8.

No, mysql has no issues with languages.
Mysql don't deal with languages. Only with encodings.
You can use any encoding supported, and utf-8 is preferred one.