https://drift-tracker.toolforge.org/report/core/ shows a schema drift for:
Mismatching field type of logging.log_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 41e752879cd906767c8473bb124345e8beb190e6#change-pVGjpnYAcwz0
There is no ready ALTER statement in the commit history.
```lang=sql
ALTER TABLE /*_*/logging
CHANGE log_timestamp log_timestamp BINARY(14) DEFAULT '19700101000000' 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: Ongoing
[] s3: Done except master (db1123)
[] s4: Done except master (db1160)
[] s5: Done except master (db1100)
[] s6: Done except master (db1173)
[] s7: Done except master (db1181)