According to T42626 the timestamp should be adjust from varbinary(14) to binary(14) because there is no need to hold infinite.
Affected columns:
cx_lists.cxl_start_time
cx_lists.cxl_end_time
cx_notification_log.cxn_date
cx_notification_log.cxn_newest
cx_corpora.cxc_timestamp
cx_translations.translation_start_timestamp
cx_translations.translation_last_updated_timestamp
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Standardise type for timestamp columns | mediawiki/extensions/ContentTranslation | master | +43 -7 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ladsgroup | T191231 RFC: Abstract schemas and schema changes | |||
| Open | None | T259374 Convert extensions to using abstract schema | |||
| Resolved | None | T261912 Convert WMF Deployed Extensions to Abstract Schema | |||
| Resolved | Umherirrender | T268543 Convert ContentTranslation to AbstractSchema | |||
| Resolved | Umherirrender | T310448 Standardise type for timestamp columns in ContentTranslation extension |
Change 804775 had a related patch set uploaded (by Umherirrender; author: Umherirrender):
[mediawiki/extensions/ContentTranslation@master] Standardise type for timestamp columns
CX Database in production is a centralized database. Not associated with a mediawiki extension update process. So these patches will need to be executed manually in CX production DB. And need to be in sync with the code deployed. cc
@KartikMistry
There is no update process for schema changes. Schema changes are handled by the DBAs, not by code deployment. The (unchanged) code works with the old and the new schema.
Change 804775 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Standardise type for timestamp columns