Don't do this | Postgres.FM 091 |

แชร์
ฝัง
  • เผยแพร่เมื่อ 31 ธ.ค. 2024

ความคิดเห็น • 6

  • @wstrzalka
    @wstrzalka 8 หลายเดือนก่อน +3

    Love your podcast. Its fun to listen for both advanced and basic topics as always something new will pop up. And the attached articles list makes waiting for the next episode more bearable 🐘

  • @TimUckun
    @TimUckun 8 หลายเดือนก่อน +1

    Why doesn’t Postgres have unsigned integers? Also why doesn’t timestamp with Timezone actually store the Timezone of the timestamp? If my app is crossing time zones I really want to know the Timezone of the writer.

  • @chralexNET
    @chralexNET 9 หลายเดือนก่อน +1

    One thing about timestamps. In my current project I only use timestamp without time zone, because I always save UTC for all my dates and times. If I do that I guess there are no problems with using timestamp without time zone then?
    Edit: Okay so reading more of the wiki article they suggest not doing that, because they think it is going to give you issues if you are going to do calculations with other timestamps that have time zones, but I am never going to do that, because all my dates and times will be in UTC.

    • @kirkwolak6735
      @kirkwolak6735 8 หลายเดือนก่อน

      I switched away from that, and one of the reasons was DST.

    • @chralexNET
      @chralexNET 8 หลายเดือนก่อน

      @@kirkwolak6735 I don't know why that would cause any issues. UTC is not affected by DST.
      What a client application does when it receives a timestamp is to work with that timestamp in UTC in its logic, and for displaying the timestamp it explicitly converts it to the local time of the client by adding the time zone offset to the timestamp.

  • @ilyaportnov181
    @ilyaportnov181 9 หลายเดือนก่อน +2

    comparasion of timestamps is nontrivial topic at all due to timezones :)