[jira] [Commented] (ROL-2133) Can't post with Emojis if using MySQL

["David Johnson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ROL-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838058#comment-16838058 ] 

David Johnson commented on ROL-2133:
------------------------------------

I did a fresh install of Roller with a new MySQL 5.7 database, took the defaults and used a conneection string with no arguments, e.g. jdbc:mysql://localhost/rollerdb and was unable to reproduce this problem. I am able to create, publish and view posts with emojis without error.

To solve this problem on blogs.apache.org, it would be helpful to know the charset used by the weblogentry table, which you can get via a query like this:

SELECT CCSA.character_set_name FROM information_schema.`TABLES` T,
                                    information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA
WHERE CCSA.collation_name = T.table_collation
  AND T.table_schema = "rollerdb"
  AND T.table_name = "weblogentry";

And: what arguments are specified in the JDBC connection string on blogs.apache.org.

[~christ] would you please run the above query (change the table_schema to match blogs.apache.org setting) and let me know what result you get?

> Can't post with Emojis if using MySQL
> -------------------------------------
>
>                 Key: ROL-2133
>                 URL: https://issues.apache.org/jira/browse/ROL-2133
>             Project: Apache Roller
>          Issue Type: Wish
>          Components: Data Model & JPA Backend
>            Reporter: David Johnson
>            Assignee: David Johnson
>            Priority: Major
>             Fix For: 5.2.3
>
>
> It is not possible to store emojis in blog posts because Roller uses the wrong default charset in MySQL. This problem is impacting blogs.apache.org INFRA-17895.
> Roller's database creation script for MySQL should use default charset utf8mb4
> If possible an safe to do, the upgrade script for 5.2.3 should use ALTER TABLE to fix that on upgrade.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)