From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Ivar Helbekkmo <tih(at)nhh(dot)no> |
Cc: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>, PostgreSQL Hackers <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] postgres and year 2000 |
Date: | 1999-01-11 07:26:51 |
Message-ID: | Pine.BSF.4.05.9901110325280.10663-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 Jan 1999, Tom Ivar Helbekkmo wrote:
> "Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>
> > We do need to handle two-digit years, [...]
>
> Is it at all possible to get away with _not_ doing so? It is, after
> all, incredibly stupid to use two-digit years in anything but spoken
> conversation, so in a way, I'd prefer computer systems to blankly
> refuse them. If they're allowed at all, I'd say parse them so that a
> year specification of '99' means the actual year 99. _Not_ 1999.
Falling back to a Unix standard...type 'cal 99' and see which year you
get :)
I agree with Tom on this...if someone types a year of 99, we should
presume that whomever entered it knew what they were entering, and/or that
the programmer of the interface had enough sense to program checks into
it...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas IZ5 | 1999-01-11 09:58:46 | WG: [HACKERS] MVCC works in serialized mode! |
Previous Message | Tom Ivar Helbekkmo | 1999-01-11 07:01:54 | Re: [HACKERS] postgres and year 2000 |