Last modified: 2010-05-15 15:48:28 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 9312 - after importing mysql database, can't edit anymore articles.QL returned error "1054:
after importing mysql database, can't edit anymore articles.QL returned error...
Status: RESOLVED DUPLICATE of bug 9311
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC Linux
: High blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
: crosswiki
Depends on:
  Show dependency treegraph
Reported: 2007-03-16 14:51 UTC by Uwe Brauer
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Description Uwe Brauer 2007-03-16 14:51:20 UTC

I installed the above mediawiki version, and can generate and edit
(new) articles.
However  when I import a backup database from another PC via the command
mysql -D wikidb < dump.sql

I can display the articles of these database, however when I try to edit an
article of these database, or even when I want to generate a new article
obtain the following error message
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 "RecentChange::save". MySQL returned error "1054:
Unknown column 'rc_old_len' in 'field list' (localhost)".

What shall I do (I think I will try out version 1.8 or earlier) but I 
would like to do, whether this behaviour is caused by some mis configuration  of 


Uwe Brauer
Comment 1 Brion Vibber 2007-03-16 14:52:04 UTC

*** This bug has been marked as a duplicate of 9311 ***
Comment 2 Uwe Brauer 2007-03-16 14:52:34 UTC
I just checked the same problem occurs in version 1.8.4 BUT NOT in 1.7.3


Uwe Brauer

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