From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Sawtell <csawtell(at)xtra(dot)co(dot)nz> |
Cc: | "Glen and Rosanne Eustace" <agree(at)godzone(dot)net(dot)nz>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Re: Problem with Dates |
Date: | 2001-01-26 15:05:15 |
Message-ID: | 29575.980521515@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Christopher Sawtell <csawtell(at)xtra(dot)co(dot)nz> writes:
> On Fri, 26 Jan 2001 12:46, Glen and Rosanne Eustace wrote:
> [ ... ]
>> template1=# select '31/12/2000'::date + '365 days'::timespan;
>> ?column?
>> ------------------------
>> 2002-01-01 00:00:00+13 <<<<<<<<<<< Wrong
>> (1 row)
> [ ... ]
> I get the same result. This business of crooked dates in NZ summertime
> is frequently because the rest of the world can't twig on to the notion that
> it is possible to have GMT + 13, and do not take account of it in date/time
> calculations.
Could one of you try it in 7.1 (beta3 or later)? We've changed some
details of the way daylight-savings transitions are handled in
date-to-timestamp conversions, so I think this might be fixed now.
It's worth checking anyway.
Also, what do you get from '31/12/2000'::date::timestamp?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-01-26 16:52:40 | Re: Rule not invoked in 7.1 |
Previous Message | John Reid | 2001-01-26 08:31:25 | Re: abstract data types? |