Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
3.3
-
MOODLE_33_STABLE
-
MOODLE_32_STABLE, MOODLE_33_STABLE
-
wip-
MDL-58729-master -
-
3.4 Sprint 1
Description
This is neither a bug nor an improvement strictly speaking but I think it would be wise to have a proper think about it.
On a database of any significant size the conversion to full unicode support is impractically slow. My test site has around 30,000 users, 8,000 courses and several years of data. Experiments (on a reasonably well specified MariaDB server) indicate that this may well take the order of several days to complete.
I'm still looking into this but it looks like the conversion may use vast amounts of disk space too. It's probably for temporary tables but if your server doesn't have it...
It's a big ask for large sites to go offline for this period of time.
I know it's optional just now but these things have a habit of being required down the line.
Attachments
Issue Links
- caused a regression
-
MDL-59561 Upgrade to 3.3 fails because of very long index in mdl_question_categories on MariaDB in utf8mb4_general_ci
-
- Closed
-
- has been marked as being related by
-
MDL-63521 Moodle installer checks for innodb_file_per_table when it probably shouldn't
-
- Open
-
-
MDL-48228 MySQL drivers only use partial UTF-8
-
- Closed
-
- will be (partly) resolved by
-
MDL-68531 Converting Database encoding with minus("-") in Database does not work
-
- Closed
-