| jcrespo added a subscriber: brion. jcrespo added a comment. |
you are essentially proposing to get rid of the recentchanges table altogether
No, I was asking to keep recentchanges as it was before, with the previous load/meaning and implement "new features" on separate tables, or on separate servers. I just gave a couple of imperfect ideas on the other ticket, if they are wrong or impossible to implement, I apologize. I was just trying to not just disable things but give options to move forward (trying to be more constructive). As I said on other ticket, I will finish the purge at T177772 and let other people discuss the right way to move forward. I wonder though, if this issue could happen on similar multiplexing patterns like MCR- and if someone has evaluate its impact. After all, even if very dissimilar situations, both start from the idea of implementing table inheritance "wrongly". But completely offtopic- that should be discussed elsewhere. CC @brion .
Cc: brion, Mattflaschen-WMF, Strainu, TerraCodes, Jay8g, Liuxinyu970226, jcrespo, Bawolff, Aklapper, hoo, daniel, Ladsgroup, Lydia_Pintscher, GoranSMilovanovic, QZanden, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
