Skip to content

Commit f6f450f

Browse files
committed
Fixes to mysql 2.0 conversion doc issue2551115 Werner Hunger
Change default chartype from utf-8 to utf8mb4 to allow emojis etc to be represented.
1 parent 17629a1 commit f6f450f

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

doc/upgrading.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,10 +77,10 @@ are more changes required for running roundup 2.0 if you choose to use
7777
python3. See `Python 3 support`_.
7878

7979
In an upgraded ``config.ini`` (see next section) the ``[rdbms]``
80-
section has a key ``mysql_charset`` set by default to ``utf-8``.
80+
section has a key ``mysql_charset`` set by default to ``utf8mb4``.
8181

82-
It should be possible to change utf-8 to any mysql charset. So if you
83-
know what charset is enabled (e.g. via a setting in ~roundup/.my.cnf,
82+
It should be possible to change ``utf8mb4`` to any mysql charset. So
83+
if you know what charset is enabled (e.g. via a setting in ~roundup/.my.cnf,
8484
or the default charset for the database) you can set it in
8585
``config.ini`` and not need to covert the database. However the
8686
underlying issues with misconverted data and bad searches will still

roundup/configuration.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1048,7 +1048,7 @@ def str2value(self, value):
10481048
(NullableOption, 'read_default_group', 'roundup',
10491049
"Name of the group to use in the MySQL defaults file (.my.cnf).\n"
10501050
"Only used in MySQL connections."),
1051-
(Option, 'mysql_charset', 'utf8',
1051+
(Option, 'mysql_charset', 'utf8mb4',
10521052
"Charset to use for mysql connection,\n"
10531053
"use 'default' for the mysql default, no charset option\n"
10541054
"is used when creating the connection in that case.\n"

0 commit comments

Comments
 (0)