Last modified: 2012-04-12 13:59:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T25604, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 23604 - Some db table created without charset and storage engine parameters
Some db table created without charset and storage engine parameters
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.16.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-05-20 07:36 UTC by Yuki Seaside
Modified: 2012-04-12 13:59 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuki Seaside 2010-05-20 07:36:23 UTC 
I've selected "InnoDB" and "MySQL 4.1/5.0 binary" on installation page, install ed successfuly.

When I view the database in phpmyadmin...

hitcounter:
charset = latin1_swedish_ci
engine = MEMORY

searchindex:
charset = latin1_swedish_ci
engine = MyISAM

Is the engine config correct? I am not sure. Anyway the charset parameter seems probably missing.
Comment 1 Chad H. 2010-05-20 18:22:13 UTC 
The storage engines are correct. For the searchindex, MyISAM is used for the fulltext search which (if I remember correctly) doesn't exist/work in InnoDB. There was some reason for the hitcounter being MEMORY instead of your selected engine, but I can't remember why offhand.

As far as the charsets, we should probably respect the user's choice.
Comment 2 Max Semenik 2010-05-20 18:40:53 UTC 
hitcounter has only one field, typed as int.
searchindex's charset is also irrelevant, because all Unicode chars are munged into an ASCII-based codes before being stored in the db for searching.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links