Last modified: 2010-05-15 15:37:55 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 1312 - command line update fails
command line update fails
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
  Show dependency treegraph
Reported: 2005-01-11 18:11 UTC by Christof Damian
Modified: 2010-05-15 15:37 UTC (History)
0 users

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


Description Christof Damian 2005-01-11 18:11:12 UTC
My database is missing some of the new tables, but they can't be installed
because it failes to early:

A database error has occurred
Query: SELECT group_name  FROM `group`  WHERE group_id='1'  LIMIT 1
Function: Group::nameFromId
Error: 1146 Table '' doesn't exist

Database.php line 345 calls wfdebugdiebacktrace()
Database.php line 297 calls databasemysql::reportqueryerror()
Database.php line 644 calls databasemysql::query()
Database.php line 662 calls databasemysql::select()
Group.php line 134 calls databasemysql::selectrow()
Group.php line 106 calls group::namefromid()
User.php line 398 calls group::newfromid()
User.php line 621 calls user::loadfromdatabase()
Setup.php line 280 calls user::getoption() line 143 calls require_once()
update.php line 11 calls require_once()
Comment 1 Brion Vibber 2005-01-29 07:47:44 UTC
Is this still present?
Comment 2 Christof Damian 2005-01-29 10:17:58 UTC
No. this bug seems to be fixed. I get a different error now, but I gave up on
command line update anyway and did it with the browser update.

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