Hacker News Reader

Still, the GP is correct about the problems.

Relational databases have exactly 1 type that corresponds to modern data-handling practices: timestamp with time zone, that stores a timestamp. There is no good way to store any other modern type, and the 1980s practices on time handling weren't actually very good.

View on HN

I'd say relational databases (in the sense of standard SQL) have 0 types that correspond to modern data-handling practices: timestamp with timezone stores an instant but lies about it and implicitly gets converted from and to the connection-local timezone.

Agreed. It's a major pain in the butt, and I wish I could just ship an int64 back and forth and not have to deal with mapping it to a calendar.

Reply on news.ycombinator.com