• lennivelkant@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Unrelated to the topic, but I deal with a database storing timestamps.

    In local time.

    For systems all around the world.

    You’ll see current entries timestamped 12:28 from eastern Europe followed by ones 6:28 from America and then another 11:28 from central Europe.

    Without offset.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 months ago

      Ew. Just store UTC timestamps and do optional translation on the client using whatever the client sets up for their timezone. It’s not hard…

      • lennivelkant@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        Oh believe me, I would change some things about that database if I could. Alas, I’m just the analyst building data models from it.

        (To be fair, it’s otherwise easy to work with and for most use-cases, it doesn’t matter since they’re aggregated per month anyway, so I just load the last month’s data on the 2nd of each month. I definitely have worse patients to operate on.)