Last modified: 2014-07-04 11:48:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13675 - Provide automated conversion to UTF-8 and binary schemas for MySQL 4.1/5.0+
Provide automated conversion to UTF-8 and binary schemas for MySQL 4.1/5.0+
Status: NEW
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-04-09 22:06 UTC by Brion Vibber
Modified: 2014-07-04 11:48 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Brion Vibber 2008-04-09 22:06:12 UTC
The MySQL 4.0-backwards-compatible default schema causes a lot of problems on MySQL 4.1 and higher:

* confusing results when doing direct queries
* difficulty sharing data with other applications
* data corruption with 'mysqldump'

The 'MySQL 5'-mode schemas avoid these problems, and are finally working properly with the standard updaters:

* The binary schema preserves full compatibility with non-BMP Unicode characters (and thus data from Wikimedia sites)

* The UTF-8 schema is limited by MySQL's BMP-only support, but still seems reasonably functional.

However, the old schema is still the default, and there's currently no provision for cross-upgrading from the old schema to one of the new ones. The installer/updater should be able to detect the old-style schema and convert. A converter maintenance script might also be helpful.

At the worst, going row-by-row and doing UTF-8 and double-UTF-8 checks and converting line-by-line should do the job. :)

Once conversion is in place, we can consider using the more capable binary schema as the default.
Comment 1 Andre Klapper 2014-07-04 11:48:25 UTC
1.18 was the last version to support MySQL 4. 
I guess this is a request that could realistically be a WONTFIX nowadays?

Note You need to log in before you can comment on or make changes to this bug.