On Monday, July 11, 2016, Daniel Kinzler daniel.kinzler@wikimedia.de wrote:
Am 11.07.2016 um 17:43 schrieb Brian Wolff:
To me, (b) makes more sense, as all the other fields in page represent
the
info for the current revision. Additionally all the fields in revision (except rev_deleted) are immutable and never change, and definitely dont change interpretation based on other db fields. Having old revisions
have a
dependency on the page table (especially a dependency going in the direction revision->page) seems wrong to me.
The question is whether you want the interpretation of that field to
depend on
another database field related to the same page, or on global
configuration.
Both seem wrong, but depending on config seems worse: in the cases where
it
happens, there is no way to fix it. A database field can at least be
updated.
I guess this ultimately comes down to fairly arbitrary opinions, but I do actually think making the interpertation dependency graph of the database that convoluted is a bigger evil then depending on global config.
-- bawolff