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

* Henk Enting (h.d.enting@mgrid.net) wrote:
> But still, I think the to_timestamp should throw an error if I put in
> something like '21-21-2011'.

I agree completely, this is a pretty big bug in my opinion.  We don't
accept invalid or garbage timestamps in the input function, I don't see
any reason why we should be allowing it in to_timestamp().  If the
values at the 'MM' location are outside of the valid range, we should be
throwing an error.

    Thanks,

        Stephen