Re: default modifiers for 7.2b4

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: mike <matrix(at)vianet(dot)ca>, PostgreSQL Mailing Lists-General <pgsql-general(at)postgresql(dot)org>, Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: default modifiers for 7.2b4
Date: 2001-12-23 05:42:46
Message-ID: 3C256ED6.E09C5EFA@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

(cross posted to -hackers, just in case...)

> or just to make it crystal clear,
> select 'foo now#&%!(at)bar'::date;

Oh yeah. From the 1.0x days of Postgres95 (and probably earlier) the
date/time parser ignored any part of a date string it didn't understand.

That has been the case, more or less, until select date 'now' ;)

As you might imagine, that could lead to Really Bad Errors, such as
ignoring mistyped time zones. So for 7.2 fields are not ignored, unless
they are on the short list of strings which have been explicitly ignored
forever. For example, 'abstime' can be inside a date string without
trouble, to support compatibility with the argument 'Invalid Abstime',
which apparently was actually emitted by Postgres or Postgres95 (or
maybe someone thought it may be someday. Who knows??!).

Anyway, the parsing has been tightened up a bit. btw, there are some new
features in the parser in addition to this, such as supporting more
varied forms of ISO-8601 dates and times.

- Thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Masaru Sugawara 2001-12-23 05:46:45 Re: getting most recent row efficiently
Previous Message Tom Lane 2001-12-23 01:56:09 Re: default modifiers for 7.2b4

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-12-23 08:07:08 Re: HISTORY file
Previous Message Tom Lane 2001-12-23 01:56:09 Re: default modifiers for 7.2b4