changeset 6333:bd84f43e1d13

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.
author John Rouillard <rouilj@ieee.org>
date Wed, 10 Mar 2021 10:35:22 -0500
parents 6a6b4651be1f
children eeddc4e03742
files doc/upgrading.txt roundup/configuration.py
diffstat 2 files changed, 5 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/doc/upgrading.txt	Thu Mar 04 12:55:21 2021 +0100
+++ b/doc/upgrading.txt	Wed Mar 10 10:35:22 2021 -0500
@@ -77,10 +77,10 @@
 python3. See `Python 3 support`_.
 
 In an upgraded ``config.ini`` (see next section) the ``[rdbms]``
-section has a key ``mysql_charset`` set by default to ``utf-8``.
-
-It should be possible to change utf-8 to any mysql charset. So if you
-know what charset is enabled (e.g. via a setting in ~roundup/.my.cnf,
+section has a key ``mysql_charset`` set by default to ``utf8mb4``.
+
+It should be possible to change ``utf8mb4`` to any mysql charset. So
+if you know what charset is enabled (e.g. via a setting in ~roundup/.my.cnf,
 or the default charset for the database) you can set it in
 ``config.ini`` and not need to covert the database. However the
 underlying issues with misconverted data and bad searches will still
--- a/roundup/configuration.py	Thu Mar 04 12:55:21 2021 +0100
+++ b/roundup/configuration.py	Wed Mar 10 10:35:22 2021 -0500
@@ -1048,7 +1048,7 @@
         (NullableOption, 'read_default_group', 'roundup',
             "Name of the group to use in the MySQL defaults file (.my.cnf).\n"
             "Only used in MySQL connections."),
-        (Option, 'mysql_charset', 'utf8',
+        (Option, 'mysql_charset', 'utf8mb4',
             "Charset to use for mysql connection,\n"
             "use 'default' for the mysql default, no charset option\n"
             "is used when creating the connection in that case.\n"

Roundup Issue Tracker: http://roundup-tracker.org/