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)
This appears to be fixed in the current sources by CVSup :-
23:16:03
Christopher Sawtell <[EMAIL PROTECTED]> writes:
> I built from sources of v-7.0.0 are there some patches somewhere, or do I
> have to d/l the whole thing via cvs?
There's no patch (if there were, it'd be enormous). Either pull from
CVS or use a beta or nightly-snapshot tarball (see pub/dev on o
On Sat, 27 Jan 2001 06:44, Glen and Rosanne Eustace wrote:
> > Could one of you try it in 7.1 (beta3 or later)?
ok, I'll have a go at upgrading. I'll try to get it done either this evening
or tomorrow. Hopefully ready on Monday.
I built from sources of v-7.0.0 are there some patches somewhere,
> Yep, you need to do whole shebang of dumping and reloading.
Hmmm.
I think I'll just cheat for a while and add 364 days, hopefully before
the end of NZ daylight savings, the production release of 7.1 will be
out. I really don't want to upgrade twice.
Glen.
On Sat, 27 Jan 2001, Glen and Rosanne Eustace wrote:
> Is 7.0.3 to 7.1B? simply a reinstall or do I need to unload/reload the
> database.
Yep, you need to do whole shebang of dumping and reloading.
-- Brett
http://www.chapelperilous.net/~bmccoy/
> regression=# select '31/12/2000'::date + '365 days'::timespan;
> ?column?
>
> 2001-12-31 00:00:00+13
> (1 row)
>
> This looks promising but I wouldn't call it conclusive, particularly
> since you're probably using a different OS than I am (I'm on HPUX
> 10.20).
On Sat, 27 Jan 2001, Glen and Rosanne Eustace wrote:
> If some one else is running 7.1 already and can just change their
> timezone to New Zealand DT and report the results it would be great.
Here ya are:
cp=> set time zone 'NZ';
SET VARIABLE
cp=> select '12/31/2000'::date + '1 year'::interval
"Glen and Rosanne Eustace" <[EMAIL PROTECTED]> writes:
> If some one else is running 7.1 already and can just change their
> timezone to New Zealand DT and report the results it would be great.
Well, with TZ set to NZST-12NZDT I get
regression=# select '31/12/2000'::date::timestamp;
?col
> 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.
I would prefer not to upgrade right at the moment, as my devel
Christopher Sawtell <[EMAIL PROTECTED]> 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
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 date
template1=# select '31/12/2000'::date;
?column?
2000-12-31
(1 row)
template1=# select '31/12/2000'::date + '365 days'::timespan;
?column?
2002-01-01 00:00:00+13<<< Wrong
(1 row)
template1=# select '31/12/2000'::date + '364 days'::time
On Thu, 25 Jan 2001, Glen and Rosanne Eustace wrote:
> pressie# select '31/12/2000'::date + '1 year'::timespan;
> ?column?
> -
> 01/01/2002 00:00:00.00 NZDT
> (1 row)
>
> pressie=#
>
> Well I do :-(
>
> I vaguely remember someone else having the same problem
On Thu, Jan 25, 2001 at 03:06:38PM +1300, Glen and Rosanne Eustace wrote:
> pressie# select '31/12/2000'::date + '1 year'::timespan;
> ?column?
> -
> 01/01/2002 00:00:00.00 NZDT
> (1 row)
What are the outputs of
select '31/12/2000'::date;
select '31/12/2000
pressie# select '31/12/2000'::date + '1 year'::timespan;
?column?
-
01/01/2002 00:00:00.00 NZDT
(1 row)
pressie=#
Well I do :-(
I vaguely remember someone else having the same problem and it was
something to do with daylight saving. I don't recall the sol
15 matches
Mail list logo
