Photos from production at ferroviasdelbajio.com/dmu/

for haskell, the biggest issue with timestamptz is that it has offsets in seconds while the time lib has offsets in minutes. so it doesn't integrate well. not many people use local mean time though.

if you use timestamp, you have to document whether it is a local time or a UTC time. with timestamptz you know it's always the session tz. so timestamptz is less ambiguous. the tz conversion is basically free, so performance isn't really a concern.

saving the same type you read is more convenient and has less SQL. you don't need to coerce the timestamptz on every read. Many db libs have better support for symmetric rather than asymmetric column access. e.g. in Haskell one type param is simpler than having one for reading and one for writing.

this is not how pgsql actually works. timestamptz doesn't _save_ the tz. it just means that you want the timestamp converted to your session tz. try 'set timezone=Asia/Tokyo' and you'll see your timestamptz change. given that you need to store the original tz anyway, may as well just use timestamp.

couple of comments for you at discourse.haskell.org/t/haskell-in...

Normalt hver år, med boghvedeblinis, fed fraiche, rødløg og dild og iskold god vodka.
Men jeg spiser ikke truede dyr, så det er forbi.

Mit indtryk lige nu er, at Putin har skabt en situation, hvor DK og alle de andre EUlande bliver nødt til at bruge mange flere penge på forsvar. Med eller uden USAs fulde støtte. Det er trist, men sådan er det.

aaaargh jeg er så træt af Bennike og hans smarte kulturanalyser. det er jo som at læse Politiken

nyt tøj skal være meget dyrere. folk skal dermed tvinges til at gå i mormors pjalter. det vil også gøre bybilledet mere farverigt da mormor ikke kun gik i gråt og sort

what are we fighting? and what did we lose in the war?

et tinder match? hehe

biler er resurceintensive uanset om de er elektriske eller ej, de bliver aldrig andet end sorte