https://bugzilla.wikimedia.org/show_bug.cgi?id=48359
--- Comment #2 from Aaron Halfaker <[email protected]> --- Well, first of all, joins are not possible (or highly impractical if performed manually) through the API. Why include any info about revisions in the recent changes table if we can get them by simply joining to the revision table? I'd argue that it's because the denormalization of the recentchanges table is useful for tracking information related to recent activity. The SHA1 field is particularly useful for tracking recent activities since it would allow me to detect reverts in (nearly) real time via the API. See my original filing of the bug to include checksum generation: https://bugzilla.wikimedia.org/show_bug.cgi?id=21860 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
