Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-55537

POLICY: Change recommended MySQL collation to case-sensitive

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 3.1.1
    • Database SQL/XMLDB, Policy
    • None
    • MOODLE_31_STABLE

      Currently Moodle recommends case-insensitive collation for MySQL database:
      https://docs.moodle.org/31/en/MySQL
      But if I create a mysql database with "recommended" collation utf8_unicode_ci I get unittest errors.
      Should not we change the recommended collation?

      There were 2 failures:
       
      1) core_dml_testcase::test_unique_index_collation_trouble
      Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.
       
      /home/marina/repositories/mdk_master/moodle/lib/dml/tests/dml_test.php:3823
      /home/marina/repositories/mdk_master/moodle/lib/phpunit/classes/database_driver_testcase.php:143
       
      To re-run:
       vendor/bin/phpunit core_dml_testcase lib/dml/tests/dml_test.php
       
      2) core_dml_testcase::test_sql_binary_equal
      SQL operator "=" is expected to be case sensitive
      Failed asserting that 2 matches expected 1.
       
      /home/marina/repositories/mdk_master/moodle/lib/dml/tests/dml_test.php:3851
      /home/marina/repositories/mdk_master/moodle/lib/phpunit/classes/database_driver_testcase.php:143
       
      To re-run:
       vendor/bin/phpunit core_dml_testcase lib/dml/tests/dml_test.php
      

      P.S. I have always actually had utf8_bin myself but changed the default collation to work on MDL-29332

            Unassigned Unassigned
            marina Marina Glancy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.