> [Postgres] just handles the pretty display for you It's rather more than that, though I don't have the time to kill digging into it now. And personally I mo

> [Postgres] just handles the pretty display for you It's rather more than that, though I don't have the time to kill digging into it now. And personally I mostly seem to end up doing more complicated date processing in code, not queries; but there everything needs to be a date immediately (not unix time or similar) for most purposes -- then I can use complicated libraries written by others to let me do "simple" things with dates, like rolling months. Ah, also: > you convert March 1st to a unix date Then that's where the complicated logic goes. Basically, you need that somewhere, and it's non-trivial (leap year calc is the least of it). My point isn't that unix dates aren't useful for storage, but that they aren't useful by themselves for calculation.