https://drift-tracker.toolforge.org/report/core/ shows a schema drift for:
Mismatching field type of revision.rev_timestamp
on s1, s2, s3, s4, s7
According to T42626 the timestamp should be adjust from `varbinary(14)` to `binary(14)` because there is no need to hold `infinite`.
The column was added in 64ac6b8e775dd8582ea9cc5f24235488f076c5b3#change-pVGjpnYAcwz0
There is no ready ALTER statement in the commit history.
```lang=sql
ALTER TABLE /*_*/revision
CHANGE rev_timestamp rev_timestamp BINARY(14) NOT NULL;
```
# **ALTERs to run:** see above
# **Where to run those changes:** s1, s2, s3, s4, s7 - list of wikis needs to be created - Please check also s5, s6, s8 before closing as the drift tracker checks a random wiki, which could pass the check, while other wikis on the same section would fail the check
# **When to run those changes:** any time
# **If the schema change is backwards compatible:** Yes
# **If the schema change has been tested already on some of the test/beta wikis:** beta cluster is running with the new schema
# **if the data should be made available on the labs replicas and/or dumps:** no change of the existing rules
Progress
[] s1: Ongoing
[] s2: Done except on master (db1162)
[] s3: Done except on master
[] s4: Ongoing
[x] s5: Done
[] s6: Done except on master
[x] s7: Done