The abstract schema at tables.json contains:
"name": "page",
"comment": "Core of the wiki: each page has an entry here which identifies it by title and contains some essential metadata.",
"columns": [
...
{
"name": "page_links_updated",
"comment": "This timestamp is updated whenever a page is re-parsed and it has all the link tracking tables updated for it. This is useful for de-duplicating expensive backlink update jobs.",
"type": "mwtimestamp",
"options": {
"notnull": false,
"default": null,
"CustomSchemaOptions": {
"allowInfinite": true
}
}
},
...In my opinion there is not need for the page_links_updated column to allow the value infinite.
The nullable and default value is okay.
This only affect mysql, where a VARBINARY(14) is used, which could be changed to BINARY(14)
abstract schema migration: 6a3aa5b5a2c91c07be669dc915cb4ba38a5a8692