Extension talk:DeletedContributions

Note that this will be pretty inefficient on large sites due to the archive table's lack of an index on the user fields. Consider adding such an index and modifying the code to use it (or at least not explicitly choose the wrong index!) for use on a custom site. --Brion VIBBER 10:34, 16 November 2006 (UTC)
 * OK, I added the index query to the page, and it now uses the right one now. I'd like to get something that is feasible on the large Wikipedia's. How expensive is it to add an index to a huge table?Voice of All 15:44, 16 November 2006 (UTC)
 * The transition time means we have to run it on slaves, switch masters, then run it again, then upgrade the software to use it. It's a bit disruptive. --Brion VIBBER 16:17, 16 November 2006 (UTC)
 * It's probably easier to not do it, then to cram all the edits in revision, archive and hidden into the revision table, with the bitfields for rev_deleted enabled. Titoxd (?!?) 04:17, 18 January 2007 (UTC)
 * That would require a long batched query and some method for determining what page is deleted. It also distances archiving from deletion, we already have nice maintenance scripts to clear the archives. Not to mention there are security issues when the database no longer enforces deletion by using a separate tables. Aaron 01:13, 23 June 2007 (UTC)

Index creation
The extension page reads: "Run the following SQL query to add a user index to the archive table (deleted revisions) if you are using a version of MediaWiki older than 1.11", yet we need to run this SQL command even with the current (alpha) version of 1.11. I think the statement needs to be rewritten. Huji 11:04, 7 July 2007 (UTC)