Skip to content

Data quality issue: 9 statements with incorrect year (4043 instead of 2022) #71

Description

@northernvariables

Hi, I discovered 9 statements in the database with an incorrect timestamp showing year 4043 instead of 2022.

Statement IDs affected: 3166444-3166452

Current (incorrect) timestamp: 4043-03-22 16:20:00+00:00Correct timestamp: 2022-02-10 17:20:00+00:00

These statements all belong to Document ID 22257 (dated 2022-02-10) and are consecutive sequences 109-117. The statements immediately before and after have the correct 2022 dates.

SQL fix:
UPDATE hansards_statement
SET time = '2022-02-10 17:20:00+00:00'
WHERE id IN (3166444, 3166445, 3166446, 3166447, 3166448, 3166449, 3166450, 3166451, 3166452);

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions