Re: BUG #6231: weird to_timestamp behaviour with out of range values

On Thu, Sep 29, 2011 at 5:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Wed, Sep 28, 2011 at 11:43 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > "Henk Enting" <h(dot)d(dot)enting(at)mgrid(dot)net> writes:
> >> I would expect the to_timestamp function to return an error when I feed
> it
> >> out of range values, e.g. months > 13 and days > 31. Instead it seems to
> add
> >> the surplus to the timestamp and then return it.
> >
> > What is your reason for using to_timestamp at all? The timestamp input
> > converter is perfectly capable of dealing with standard formats like
> > yyyy-mm-dd, and it does what most people expect in the way of data
> > validation checks.
>
> Well, you might want to insist that the input is in some particular
> format, rather than just "whatever the input function will accept"...
>
Exactly. But I probably can rely on the input function and set the datastyle
parameter to make sure I get the right dates (e.g. in our case 07-04-2011is
in april, not in july).
But still, I think the to_timestamp should throw an error if I put in
something like '21-21-2011'.

Best Regards,

Henk Enting