Skip to content

data-too-old: check columns with non-timestamp types, but with "time" in their names#128

Merged
macbre merged 1 commit intomasterfrom
data-too-old-more-time-columns
Mar 11, 2018
Merged

data-too-old: check columns with non-timestamp types, but with "time" in their names#128
macbre merged 1 commit intomasterfrom
data-too-old-more-time-columns

Conversation

@macbre
Copy link
Owner

@macbre macbre commented Mar 11, 2018

data_not_updated_recently → table affected: 0028_revision

✗ "0028_revision" has the latest row added 69 days ago, consider checking if it should be up-to-date

  - diff_days: 69
  - data_since: 2018-01-01 00:00:00
  - data_until: 2018-01-01 00:00:00
  - date_column_name: rev_timestamp
  - schema: CREATE TABLE `0028_revision` (
      `rev_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
      `rev_timestamp` binary(14) NOT NULL,
      PRIMARY KEY (`rev_id`)
    ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1
  - rows: 1
  - table_size_mb: 0.015625

Check MediaWiki tables columns that use CHAR(14) instead of DATETIME - see why.

@macbre macbre added the linters label Mar 11, 2018
@macbre macbre added this to the v1.2 milestone Mar 11, 2018
@macbre macbre changed the title data-too-old: check columns with non-timestamp values, but with "time" in their names data-too-old: check columns with non-timestamp types, but with "time" in their names Mar 11, 2018
@macbre macbre merged commit 459c0f0 into master Mar 11, 2018
@macbre macbre deleted the data-too-old-more-time-columns branch March 11, 2018 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant