Bug 1186681

Wondering what version of the driver is used - locally I used:

mysql-connector-java:5.1.18

I'm assigning this bug to xPaaS team, since they own this cartridge.

well, the problem is not really the mobile cartridge. The problem is that the mysql server is NOT configured with utf8mb4

Matthias Wessendorf <matthias> updated the status of jira AGPUSH-1246 to Coding In Progress

The default encoding for newly created databases is utf8 (see [1]). We'd like to keep that default. Since each user is able to login into his gear and change database encoding using commands from [2] I'm closing this as a won't fix.

[1] https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/post_install#L14
[2] http://dba.stackexchange.com/questions/8239/how-to-easily-convert-utf8-tables-to-utf8mb4-in-mysql-5-5/21684#21684

When the cartridge is launch, why can we not change the MySQL server, that will be used (and created) on this cart ? 

We do need that

Here is some more info:
http://info.michael-simons.eu/2013/01/21/java-mysql-and-multi-byte-utf-8-support/

But locally, I don't even set this, and it works. What version of the mysql driver is used?

Please have a look at this:
http://dev.mysql.com/doc/connector-j/en/connector-j-reference-charsets.html

Setting the Character Encoding
The character encoding between client and server is automatically detected upon connection. You specify the encoding on the server using the character_set_server for server versions 4.1.0 and newer, and character_set system variable for server versions older than 4.1.0. The driver automatically uses the encoding specified by the server. For more information, see Server Character Set and Collation.

For example, to use 4-byte UTF-8 character sets with Connector/J, configure the MySQL server with character_set_server=utf8mb4, and leave characterEncoding out of the Connector/J connection string. Connector/J will then autodetect the UTF-8 setting.

To override the automatically detected encoding on the client side, use the characterEncoding property in the URL used to connect to the server.


HERE IS MY PROBLEM:

* The OpenShift cartridge sets the `character_set_server` to `latin1`
* I should be able to override the `characterEncoding` property on the URL to override this, however it does not accept `utf8mb4`:

java.sql.SQLException: Unsupported character encoding 'utf8mb4'

MySQL does not seem to think it's needed to fix this:
http://bugs.mysql.com/bug.php?id=64823

So now I'm stuck. It seems we can't use utf8mb4 on OpenShift due to this??

"The default encoding for newly created databases is utf8 (see [1]). We'd like to keep that default."

Why would you like to keep that default? It is wrong.
Please note that `utf8` on MySQL is not the good old utf8 that we all know and love. Instead it's a broken, 3-byte, MySQL-specific encoding that MySQL calls `utf8`. The encoding we all know and love as `utf8` is actually called `utf8mb4` in MySQL.

Read more:
https://stijndewitt.wordpress.com/2015/06/15/use-mysql-utf8mb4-if-you-want-full-unicode-support/

We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.