Last modified: 2010-05-15 15:33:18 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 3053 - "Recent Changes" complains about mySQL for some users
"Recent Changes" complains about mySQL for some users
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.4.x
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-05 10:07 UTC by Mark Brier
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Attachments

Description Mark Brier 2005-08-05 10:07:08 UTC
Both the sysop user AND my personal user are unable to use the "Recent Changes"
special page. A new user was able to use the function without problems (after
restoring preferences to defaults for the affected users, the result is the same). 

The error shown is as follows...

Database error
A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

    (SQL query hidden)

from within function "wfSpecialRecentchanges". MySQL returned error "1030: Got
error 127 from table handler (localhost)
Comment 1 Antoine "hashar" Musso (WMF) 2005-08-05 22:14:24 UTC
"MySQL error code 127: Record-file is crashed"

You need to repair the recentchanges table. See:
http://dev.mysql.com/doc/mysql/en/repair.html

Comment 2 Mark Brier 2005-08-08 08:24:12 UTC
Thanks v much, this fixed it!

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


Navigation
Links