From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John Cochran <jdc(at)fiawol(dot)org> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: timestamp patch to extend legal range of dates. |
Date: | 2003-02-04 04:41:13 |
Message-ID: | 2890.1044333673@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
John Cochran <jdc(at)fiawol(dot)org> writes:
> Here is a patch that modifies how timestamp values are generated and
> extends the legal range of timestamps. The overall effect is:
> 1. For dates prior to Oct 15, 1582 it uses the Julian calendar.
> 2. For dates on and after Oct 15, 1582, it uses the Gregorian calendar.
>
> The decision to have the switchover point be Oct 15, 1582 was made to cause
> the new routines return the same values as the old routines for the largest
> possible range. I did consider having the switchover be Sept 14, 1752 to
> be consistent with Unix, but decided against it.
This seems like rather an odd choice. Isn't the 1752 date commonly
recognized as the start of Gregorian dating?
I'd be inclined to go with a changeover date that's defensible in the
long run, without regard to what we might have done before. Backwards
compatibility with mistakes isn't a good design principle IMHO ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2003-02-04 11:17:37 | Patch Applied question about rollback and SQLException |
Previous Message | Neil Conway | 2003-02-04 02:26:47 | Re: timestamp patch to extend legal range of dates. |