Last modified: 2013-09-04 11:51:30 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 T31590, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29590 - Installer should sanity check pre-existing tables
Installer should sanity check pre-existing tables
Status: NEW
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.17.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-26 01:17 UTC by Edward Z. Yang
Modified: 2013-09-04 11:51 UTC (History)
1 user (show)

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


Attachments

Description Edward Z. Yang 2011-06-26 01:17:23 UTC
Consider the following database, which we would like to install MediaWiki onto:

mysql> show tables;
+----------------------------------------------+
| Tables_in_wizard_test_mediawiki_install_head |
+----------------------------------------------+
| user                                         |
+----------------------------------------------+
1 row in set (0.00 sec)

There's a single user table here, ostensibly left over from a failed install. OK, that's fine. How does the installer cope? It claims "config-install-tables-exist", and then cheerfully attempts to access 'interwiki' table, which doesn't exist.

Ironically, the user table is unconditionally created.

Ideally, DatabaseInstaller->createTables should sanity check the existing tables and error out with something more reasonable if they don't match up with the schema, or complain that you should rather be using the ugprader.

You can treat this as a feature request. Probably.

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


Navigation
Links