Updated date/time parsing

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Updated date/time parsing
Date: 2001-12-29 18:55:55
Message-ID: 3C2E11BB.CD1A1D05@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I've committed changes to tighten up the date/time parsing, while
enabling more edge cases which should have worked but didn't. The
changes have the following effects:

1) date fields like "2001-12-29" need the same delimiter between all
fields. Previously, any of "-", "/", or "." might have been accepted;
now the second delimiter must match the first.

2) Julian day actually works for both input (with a leading "J") and
output (using EXTRACT('julian' from timestamp)).

3) the ISO-8601 identifier for time fields ("T") now works for all cases
I can think of to test. So '20011227T040506.789' and other variants now
are recognized.

4) more cases of time zones are interpreted correctly. Previously, some
cases were sensitive to leading spaces or lack thereof.

5) regression tests still pass, and I have some additional regression
test cases to add after the upcoming 7.2 release (and those pass too).

- Thomas

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-12-29 19:10:43 LWLock contention: I think I understand the problem
Previous Message Tom Lane 2001-12-29 16:54:39 Re: TODO question