Last modified: 2011-07-18 20:50:10 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 T26904, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24904 - An incomplete Renameuser job has made the Revision table inconsistent
An incomplete Renameuser job has made the Revision table inconsistent
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
http://ja.wikipedia.org/?oldid=330922...
:
Depends on:
Blocks: 29757
  Show dependency treegraph
 
Reported: 2010-08-22 14:39 UTC by Kanjy
Modified: 2011-07-18 20:50 UTC (History)
3 users (show)

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


Attachments

Description Kanjy 2010-08-22 14:39:59 UTC
I am [[w:ja:User:Kanjy]], a Bureaucrat at Japanese Wikipedia.  Last month I changed username of a user who made about 10,900 contributions, as per requested.  Although most of his contributions moved to the new username within a day, 500 edits are still with his old username.  In the Revision table of the database, the "rev_user_text" field of the 500 revisions are not updated yet.

Could anyone fix this inconsistency in the Revision table?

The user id: 36207
The new username: Pastern
http://ja.wikipedia.org/wiki/Special:Contributions/Pastern

The old username: 廉
http://ja.wikipedia.org/wiki/Special:Contributions/%E5%BB%89

Thank you.
-- w:ja:User:Kanjy
Comment 1 Aaron Schulz 2010-10-08 23:34:38 UTC
Has this been fixed yet?
Comment 2 Ariel T. Glenn 2011-07-10 17:20:53 UTC
I've run a script to move these edits. Please check to see that things look correct and let me know.
Comment 3 Mark A. Hershberger 2011-07-18 20:50:10 UTC
no response -> fixed

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


Navigation
Links