Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f34Gaw852670 for ; Wed, 4 Apr 2001 12:36:58 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f34Garw06256; Wed, 4 Apr 2001 12:36:53 -0400 (EDT) To: "Albert REINER" cc: PostgreSQL-SQL Subject: Re: Historical dates in Timestamp In-reply-to: <20010404130423.A2180@frithjof> References: <20010404130423.A2180@frithjof> Comments: In-reply-to "Albert REINER" message dated "Wed, 04 Apr 2001 13:04:23 +0200" Date: Wed, 04 Apr 2001 12:36:53 -0400 Message-ID: <6253.986402213@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/50 X-Sequence-Number: 2389 "Albert REINER" writes: > Is it really reasonable to enforce that the number of years is four > digits at least? I believe so. Without that cue it's pretty difficult for the timestamp parser even to figure out which field is intended to be the year, let alone whether you'd like 1900 or 2000 added to a two-digit year value. For example, with the default datestyle: regression=# select '12-5-28'::timestamp; ?column? ------------------------ 2028-12-05 00:00:00-05 (1 row) regression=# select '0012-5-28'::timestamp; ?column? --------------------- 0012-05-28 00:00:00 (1 row) regards, tom lane