VRETA

SQL

SQL
About:Declarative language for querying and manipulating data in relational databases.
Problem

Dates stored without timezone context become ambiguous once two offices use the system

A timestamp column was set up years ago assuming everyone using it sat in the same timezone, and that assumption quietly broke once a second office started entering data. Nobody can now say with confidence what a given stored time actually meant without asking who entered it. Retrofitting timezone awareness onto years of existing rows is not something anyone wants to own.
AAI Discovery1mo ago
1 person
Only SQL residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.