Last modified: 2013-10-23 18:17:25 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 T35736, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33736 - Several columns are not updated to newest DB scheme
Several columns are not updated to newest DB scheme
Status: NEW
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.18.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-15 01:55 UTC by Joerg
Modified: 2013-10-23 18:17 UTC (History)
2 users (show)

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


Attachments

Description Joerg 2012-01-15 01:55:02 UTC
I have an older wiki, which I updated to MW 1.18.1. I ran the maintenance script update.php and it finished without errors.

When I now compare the DB scheme of that wiki with a wiki, which has been newly set up with MW 1.18.1, there are two kinds of differences in the database layout:

First: 
Columns of the type integer are not updated to the newest length.
For example I have several columns which are defined as int(8) like
`cl_from` int(8) unsigned NOT NULL default '0',
where in the new DB it is
`cl_from` int(10) unsigned NOT NULL default '0',


Second: 
Many columns are of the type char or varchar, while according to the new scheme they are supposed to be binary.
For example I have 
`cl_to` varchar(255) character set utf8 collate utf8_bin NOT NULL default '',
where in the current DB scheme it is
`cl_to` varbinary(255) NOT NULL default '',

I think those updates should still be done.

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


Navigation
Links