JCR MySQL-backend requires special dialect MySQL-UTF8 to be used for internationalization support. But the database default charset should be latin1 to use limited index space effectively (1000 bytes for MyISAM engine, 767 for InnoDB). If database default charset is multibyte, a JCR database initialization error is thrown concerning index creation failure. In other words, JCR can work on any singlebyte default charset of database, with UTF8 supported by MySQL server. But we have tested it only on latin1 database default charset.

Repository configuration, workspace container entry example:

<workspace name="collaboration">

          <container class="org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer">

            <properties>

              <property name="source-name" value="jdbcjcr" />

              <property name="dialect" value="mysql-utf8" />

              <property name="multi-db" value="false" />

              <property name="max-buffer-size" value="200k" />

              <property name="swap-directory" value="target/temp/swap/ws" />

            </properties>

          .....