Re: date comparisons - Mailing list pgsql-general

From Tom Lane
Subject Re: date comparisons
Date
Msg-id 5052.1165944322@sss.pgh.pa.us
Whole thread Raw
In response to Re: date comparisons  ("Belinda M. Giardine" <giardine@bio.cse.psu.edu>)
Responses Re: date comparisons  ("Belinda M. Giardine" <giardine@bio.cse.psu.edu>)
Re: date comparisons  (Richard Huxton <dev@archonet.com>)
Re: date comparisons  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general
"Belinda M. Giardine" <giardine@bio.cse.psu.edu> writes:
> Should it be this way?

Well, to_timestamp() is apparently designed not to complain when the
input doesn't match the format, which is not my idea of good behavior
... but your example is in fact wrong.  'Month' means a 9-character
field, so you are short a couple of spaces.

regression=# select to_timestamp('January 2006', 'Month YYYY');
      to_timestamp
------------------------
 0006-01-01 00:00:00-05
(1 row)

regression=# select to_timestamp('January   2006', 'Month YYYY');
      to_timestamp
------------------------
 2006-01-01 00:00:00-05
(1 row)

You probably want

regression=# select to_timestamp('January 2006', 'FMMonth YYYY');
      to_timestamp
------------------------
 2006-01-01 00:00:00-05
(1 row)

Or, as suggested upthread, forget to_timestamp and just use the native
timestamp or date input conversion, which on the whole is a lot more
robust (it *will* throw an error if it can't make sense of the input,
unlike to_timestamp).

            regards, tom lane

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Restore database from files (not dump files)?
Next
From: Paul Silveira
Date:
Subject: Re: shell script to populate array values