Subject | Re: [firebird-support] Date Range |
---|---|
Author | Ann W. Harrison |
Post date | 2005-01-11T20:07:53Z |
Lester Caine wrote:
adjustment for the change from the Julian calendar.
of days that should be added to the base date to get the desired data.
If it's negative, it goes backward. The base date is 17 November 1858.
(Long story omitted as boring and pointless). There are plenty of
digits to go back earlier than 0100-01-01 and forward beyond 9999. The
restriction comes from the string representation and the difficulty we
had in distinguishing between '01/01/01' meaning the first day of the
modern era and '01/01/01' meaning the first of January 2001. I thought
you should be able to write '01/01/0001'. Jim thought that leading
zeros were not significant. We discussed it. I changed the
documentation.
Regards,
An
> OK date range is quoted as 0100-01-01 to 9999-12-31That's just the count of days using the Gregorian calendar. There's no
> Is that to the Gregorian calendar, or will there be errors in day counts
> against the Gregorian calendar?
adjustment for the change from the Julian calendar.
>Arrg. The date data type has one 32 bit word that contains the number
> Of cause in theory I need dates before the year 0100 - If I can find any
> ancestors dates from roman times ;)
of days that should be added to the base date to get the desired data.
If it's negative, it goes backward. The base date is 17 November 1858.
(Long story omitted as boring and pointless). There are plenty of
digits to go back earlier than 0100-01-01 and forward beyond 9999. The
restriction comes from the string representation and the difficulty we
had in distinguishing between '01/01/01' meaning the first day of the
modern era and '01/01/01' meaning the first of January 2001. I thought
you should be able to write '01/01/0001'. Jim thought that leading
zeros were not significant. We discussed it. I changed the
documentation.
Regards,
An