Last modified: 2011-03-13 18:05:41 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 T13961, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 11961 - Database error in article history at Wikipedia article "History of Knitting"
Database error in article history at Wikipedia article "History of Knitting"
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/w/index.php?t...
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-13 11:35 UTC by Willow
Modified: 2011-03-13 18:05 UTC (History)
1 user (show)

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


Attachments

Description Willow 2007-11-13 11:35:04 UTC
The "earliest" edit for the English Wikipedia article, "History of knitting" appears to be out of order, referring to an edit that occurred probably two years after the true first edit, which is listed as the 2nd earliest edit.  

More specifically, the true first edit was done by user AmyNelson on 11 September 2004, whereas the false first edit was done by Daylilly probably around 10 March 2005 (by moving to the next and previous revisions) although it's listed in the article history as occurring on 4 January 2003.  If you could fix that, that'd be great! :)

Willow
Comment 1 Willow 2007-11-13 11:39:06 UTC
Oops, I see that I made a minor bug myself in my first paragraph! I meant to say that the Daylilly edit is listed in the database as having a date (4 January 2003) two years earlier than when it actually occurred (~10 March 2005).  Thanks!
Comment 2 Domas Mituzas 2007-11-13 11:51:17 UTC
unfortunately we used to have clocks skewed on our application servers back in 2005 :) due to revision IDs not being sequential it is pretty much pain to fix all that automatically, and we let it live. :)

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


Navigation
Links