Change Details

According to https://drift-tracker.toolforge.org/report/checkuser/, the `cul_timestamp` column in the `cu_log` table has multiple drifts indicating that the DBs have the wrong column type. I do not know whether this drift is reported correctly, but if there is a mismatch in column type this should be fixed. The correct column type for this is `mwtimestamp` which on MariaDB is `BINARY(14) NOT NULL`.

According to https://drift-tracker.toolforge.org/report/checkuser/, the `cul_timestamp` column in the `cu_log` table has multiple drifts indicating that the DBs have the wrong column type. I have verified that this drift exists for a DB on s1. The correct column type for this is `mwtimestamp` which on MariaDB is `BINARY(14) NOT NULL`.

According to https://drift-tracker.toolforge.org/report/checkuser/, the `cul_timestamp` column in the `cu_log` table has multiple drifts indicating that the DBs have the wrong column type. I do not know whether this drift is reported correctly, but if there is a mismatch in column type this should be fixedI have verified that this drift exists for a DB on s1. The correct column type for this is `mwtimestamp` which on MariaDB is `BINARY(14) NOT NULL`.