Last modified: 2011-05-03 18:57:00 UTC
Special:Export and Special:Import currently do not handle revision tags. There are plenty of reasons, why they should handle them, at least optionally.
Removing i18n, has nothing to do with that.
Should be straightforward to add them to the export format at least.
Should we include them in the export unconditioally, or rather have the exporter ask for them in the export form? After all, they cost an extra query per revision.
I believe we've got a summary table which can be left-joined, which'll pull the info in with the main query.
Yes. I was thinking that this also would increase the query result size considerably, but real data suggests not so. There are hardly any such tags at all, and even less occasions where there are several tags to a single revision. Nevertheless, there may be more than 1 result row for one revision with the join, which makes loop control over rows more complicated.
The tag_summary has one row per revision for exactly this reason, so there's no change to loop control.
Givng dump bugs to Ariel.