From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: to_char() accepting invalid dates? |
Date: | 2011-07-18 22:02:27 |
Message-ID: | 201107182202.p6IM2Ri03591@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Thomas Kellerer wrote:
> Jasen Betts wrote on 18.07.2011 11:23:
> >> postgres=> select to_date('20110231', 'yyyymmdd');
> >>
> >> to_date
> >> ------------
> >> 2011-03-03
> >> (1 row)
> >>
> >> is there a way to have to_date() raise an exception in such a case?
> >
> > it's possible the odd behaviour you get is required by some standard.
>
> That would be *very* odd indeed.
>
>
> > jasen=# select '20110303'::date;
> Thanks for the tip, this was more a question regarding _why_ to_char() behaves this way.
Well, to_char() is based on Oracle's to_char(). How does Oracle handle
such a date?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2011-07-19 11:30:42 | Re: to_char() accepting invalid dates? |
Previous Message | Thomas Kellerer | 2011-07-18 17:07:43 | Re: to_char() accepting invalid dates? |