Am 16.09.2017 um 01:22 schrieb Matthew Flaschen:
On 09/15/2017 06:51 AM, Daniel Kinzler wrote:
Also, I believe Roan is currently looking for a better mechanism for tracking all kinds of reverts directly.
Let's see if we want to use rev_sha1 for that better solution (a way to track reverts within MW itself) before we drop it.
The problem is that if we don't drop is, we have to *introduce* it for the new content table for MCR. I'd like to avoid that.
I guess we can define the field and just null it, but... well. I'd like to avoid that.