From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Aspire Something <aspire420(at)hotpop(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: [BUGS] Date Return must be As per Natural Calander |
Date: | 2003-02-25 04:06:38 |
Message-ID: | 7495.1046145998@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-bugs |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> I guess adding 1 day to 1752-09-02 should give us 1752-09-14, but your
> right, it gives us 1752-09-03.
As was pointed out at length just recently, the transition from Julian
to Gregorian calendars happened at different times in different places.
So the above claim is only correct for some places.
The conclusion from the previous discussion was that our existing
behavior (extrapolate Gregorian rules backwards indefinitely) is as
defensible as anything else that would be likely to get coded.
I suppose you could imagine something that looks at the locale and
tries to guess the appropriate transition date ... but I don't foresee
anyone getting very excited about coding it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2003-02-25 06:47:37 | postings appearing twice... |
Previous Message | mlaks | 2003-02-25 03:12:22 | Its not a bug its a feature! Re: Date Return must be As per Natural Calander |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-25 05:44:21 | Re: Bug #903: Performance Hangs during Lookups |
Previous Message | mlaks | 2003-02-25 03:12:22 | Its not a bug its a feature! Re: Date Return must be As per Natural Calander |