date/time formats in 7.2

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Hackers List <pgsql-hackers(at)postgresql(dot)org>, General Postgres List <pgsql-general(at)postgresql(dot)org>
Subject: date/time formats in 7.2
Date: 2001-12-29 03:39:42
Message-ID: 3C2D3AFE.5482731A@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

For 7.2, to support some ISO-8601 variants, I'm tightening up the date
delimiter parsing to require the same delimiter to be used between all
parts of a date.

Does anyone use the German date notation for PostgreSQL? If so, what is
the actual format you input? The reasons I'm asking are:

o I had recalled that the format was "dd.mm/yyyy", but actually
PostgreSQL emits "dd.mm.yyyy".

o By tightening up the parsing, "dd.mm.yyyy" would be accepted, but
"dd.mm/yyyy", "yyyy.mm-dd", etc would not.

o The stricter parsing in this area would allow more general parsing
elsewhere, enabling other variants such as

yyyymmddThhmmss
yyyymmdd hhmmss.ss-zz
Thhmmss-zz

With these changes, more formats should be correctly handled, including
some edge cases which should have worked but seemed not to; the current
regression tests still all pass. As an example of edge case troubles,
7.1 accepts both of the following:

timestamp '2001-12-27 04:05:06-08'
timestamp '2001-12-27 040506 -08'

But rejects the latter if the space before the time zone is removed:

timestamp '2001-12-27 040506-08'

Comments? Suggestions?

- Thomas

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2001-12-29 04:55:19 Re: Problem (bug?) with like
Previous Message Nate Haggard 2001-12-28 23:13:11 trigger is holding up the data

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-12-29 03:44:50 Re: TODO question
Previous Message Tom Lane 2001-12-29 00:15:08 Re: TODO question