Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1378

Setup Wizard for MySQL connection doesn't specify characterEncoding

XMLWordPrintable

      Since we only support latin1 encoding at the moment for MySQL, we should specify in the connection JDBC URL characterEncoding=latin1 and useUnicode=true. This is important if the users have installed their MySQL to use UTF8 as their default encoding. If this isn't implemented, it can lead to illegal collation errors.

      This should be revisited after implementing utf8 support in Crowd for MySQL.

      useUnicode=true sounds a bit counter-intuitive but according to MySQL's docs, the characterEncoding parameter is only evaluated if useUnicode is true.

            [CWD-1378] Setup Wizard for MySQL connection doesn't specify characterEncoding

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1510624 ] New: JAC Bug Workflow v3 [ 3365195 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1390445 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1510624 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273055 ] New: Simplified Crowd Development Workflow v2 [ 1390445 ]
            jawong.adm made changes -
            Workflow Original: JIRA Bug Workflow v2 [ 174104 ] New: Crowd Development Workflow v2 [ 273055 ]
            Justin Koke made changes -
            Workflow Original: jira [ 149853 ] New: JIRA Bug Workflow v2 [ 174104 ]
            shihab made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            David Yu made changes -
            Description Original: Since we only support latin1 encoding at the moment for MySQL, we should specify in the connection JDBC URL *characterEncoding=latin1* and *useUnicode=true*. This is important if the users have installed their MySQL to use UTF8 as their default encoding. If this isn't implemented, it can lead to [illegal collation errors|http://confluence.atlassian.com/pages/viewpage.action?pageId=179077288].

            This should be revisited after implementing utf8 support in Crowd for MySQL.             		New: Since we only support latin1 encoding at the moment for MySQL, we should specify in the connection JDBC URL *characterEncoding=latin1* and *useUnicode=true*. This is important if the users have installed their MySQL to use UTF8 as their default encoding. If this isn't implemented, it can lead to [illegal collation errors|http://confluence.atlassian.com/pages/viewpage.action?pageId=179077288].

            This should be revisited after implementing utf8 support in Crowd for MySQL.

            useUnicode=true sounds a bit counter-intuitive but according to [MySQL's docs|http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html], the characterEncoding parameter is only evaluated if useUnicode is true.

            David O'Flynn [Atlassian] made changes -
            Fix Version/s New: 1.6.1 [ 14395 ]
            David Yu made changes -
            Link New: This issue relates to CWD-990 [ CWD-990 ]
            David Yu created issue -

              doflynn David O'Flynn [Atlassian]
              davidyu David Yu
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: