From 3df7baf0d2edb018b76929e4f9f4a96b090b6693 Mon Sep 17 00:00:00 2001 From: Tim Starling Date: Wed, 9 Jul 2008 06:20:52 +0000 Subject: [PATCH] Remove "experimental" tag from MySQL 4.1+ character set options, and warn users against using the "backwards-compatble" mode instead, which, it turns out, is a whole lot worse than any problem we've ever had with the so-called experimental modes. Make mysql5-binary the default. Explain the difference between the two 4.1+ modes. --- config/index.php | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/config/index.php b/config/index.php index 591f7d68fb..1c1d3877c9 100644 --- a/config/index.php +++ b/config/index.php @@ -602,7 +602,7 @@ print "
  • Environment check ## MySQL specific: $conf->DBprefix = importPost( "DBprefix" ); $conf->setSchema( - importPost( "DBschema", "mysql4" ), + importPost( "DBschema", "mysql5-binary" ), importPost( "DBengine", "InnoDB" ) ); ## Postgres specific: @@ -1421,16 +1421,17 @@ if( count( $errs ) ) {
    Select one:
      -
      • -
      • -
      • +
      • +
      • +

    - EXPERIMENTAL: You can enable explicit Unicode charset support - for MySQL 4.1 and 5.0 servers. This is not well tested and may - cause things to break. If upgrading an older installation, leave - in backwards-compatible mode. + This option is ignored on upgrade, the same character set will be kept. +

    + WARNING: If you use backwards-compatible UTF-8 on MySQL 4.1+, and subsequently back up the database with mysqldump, it may destroy all non-ASCII characters, irreversibly corrupting your backups!. +

    + In binary mode, MediaWiki stores UTF-8 text to the database in binary fields. This is more efficient than MySQL's UTF-8 mode, and allows you to use the full range of Unicode characters. In UTF-8 mode, MySQL will know what character set your data is in, and can present and convert it appropriately, but it won't let you store characters above the Basic Multilingual Plane.

    -- 2.20.1