3 ms·
Well, you'll need another type meaning "local time" for #1. That's not a time without time zone, it's an entirely different thing. Most environments simply can
by marcosdumay 3y ago
Well, you'll need another type meaning "local time" for #1. That's not a time without time zone, it's an entirely different thing.
Most environments simply can't represent that thing. They never could. With those changes this becomes more obvious, and with some luck people will finally fix this.
(The most absurd case is the "timestamp with local time zone" from SQL, that reads exactly like what you want, but represents a timestamp in a specific time zone, that is discoverable but mostly unknown.)
- int_19h 3y ago"8AM local time" is exactly time without a timezone. It's not datetime without timezone, but that's a different question.
- marcosdumay 3y agoWell, you seem to have some weird definition for the word "exactly". "8AM" is exactly time without a timezone. "8AM at local time (local defined by this procedure)" isn't exactly that. Perhaps you mean something like homomorphic. It is almost perfectly homomorphic. But if you define your types that way, you'll push yourself into the most useless ones you can get quite quickly.