Page MenuHomePhabricator

Moving sha1 into revision tag in XML dumps
Closed, ResolvedPublic


Moves SHA1 sums into revision tags

Currently, each /page/ tag has the sha1 sum of the first (i.e.: not necessarily current) /revision/'s text added. The revision tags do not come with SHA1 tags.

While there is nothing wrong with this, the export-0.6 XML schema requires the SHA1 sum of each revision to be stored within the corresponding /revision/ tag itself.

The supplied patch moves the sha1 sum from the page tag to the revision tag.

Version: 1.19
Severity: enhancement




Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:11 AM
bzimport set Reference to bz34963.

See r109848#c31769, making this under 1.19, because it is new in 1.19 and should by fixed now, to have the xsd and xml matched closure each other.

It is nice to get this fixed now, because than there is no problem with b/c in some years (or want you add this to page and revision for b/c? That makes the dump bigger, please avoid that). The xsd already says it is at the revision and the value is in the database for each revision. There is no reason do not move the lines from one method to the other.

  • Bug 35265 has been marked as a duplicate of this bug. ***

Marking 1.19wmf1 since we will likely backport this.