Re: A creepy story about dates. How to prevent it? - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: A creepy story about dates. How to prevent it?
Date
Msg-id Pine.LNX.4.44.0306192142500.2087-100000@peter.localdomain
Whole thread Raw
In response to Re: A creepy story about dates. How to prevent it?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A creepy story about dates. How to prevent it?
Re: A creepy story about dates. How to prevent it?
List pgsql-general
Tom Lane writes:

> It would make sense to offer a "strict" mode in which the date order
> has to be what DateStyle suggests.  I'm astonished that no one seems
> to get the point that there are also good uses for "lax" parsing.

There are different kinds of lax parsing.

Lax parsing is great if you can enter any of

January 8, 1999
1999-01-08
1/8/1999
990108
January 8 04:05:06 1999 PST

and it will know what you mean, because of all these have their uses and
are unambiguous (given a known day/month order).

But automatically switching the declared day/month order based on
heuristics is not that great.  A human is not going to mentally switch his
preferred day/month order within the same SQL session.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-general by date:

Previous
From: "Nigel J. Andrews"
Date:
Subject: Re: Incremental backups, and backup history
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: Getting one row for each subquery row...?