From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
Cc: | Michael Glaesemann <grzm(at)seespotcode(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Calculating the difference between timetz values |
Date: | 2009-07-27 17:49:41 |
Message-ID: | 13123.1248716981@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alexey Klyukin <alexk(at)commandprompt(dot)com> writes:
> On Jul 27, 2009, at 6:52 PM, Michael Glaesemann wrote:
>> I don't have a solution, but am curious what your use case is for
>> timetz (as opposed to timestamptz).
> I'm writing a custom trigger function that has to compare values of
> time* types and make some actions depending on a result.
It's still fairly unclear why you think that comparing timetz values
is a useful activity. Is "23:32" earlier or later than "00:32"?
How can you tell whether it's the same day or different days? Adding
timezones into that doesn't make it better.
Our documentation deprecates timetz as a poorly-defined datatype,
and I've never seen a reason to argue with that judgment. I'd suggest
taking a very hard look at why you're not using timestamptz instead.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-07-27 18:45:45 | Re: Relational Algebra and Aggregate Functions |
Previous Message | Joshua D. Drake | 2009-07-27 17:39:41 | Re: Postgres and multiple updates in one statement |