RE: TO_DATE Function unintended behavior when month value is greater than 12

From: Igor Neyman <ineyman(at)perceptron(dot)com>
To: naidu rongali <rongalinaidu(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: RE: TO_DATE Function unintended behavior when month value is greater than 12
Date: 2018-03-01 19:28:44
Message-ID: CO2PR17MB0058CA3B1C32ECCEBAC4BD66DAC60@CO2PR17MB0058.namprd17.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


From: naidu rongali [mailto:rongalinaidu(at)gmail(dot)com]
Sent: Thursday, March 01, 2018 1:34 PM
To: pgsql-bugs(at)postgresql(dot)org
Subject: TO_DATE Function unintended behavior when month value is greater than 12

Attention: This email was sent from someone outside of Perceptron. Always exercise caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.

Hi,
I noticed this behavior on recent release of PG database. It will be helpful to users, if this behavior is looked into.

When executed below SQL, got unintended output when i expected it to throw error " not a valid month "

SQL executed:
select to_date('20171231','YYYYDDMM')

result:
2019-07-17

Thank you, Naidu

I get this:
ERROR: date/time field value out of range: "20171231" SQL state: 22008

Regards,
Igor Neyman

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pantelis Theodosiou 2018-03-01 19:40:10 Re: TO_DATE Function unintended behavior when month value is greater than 12
Previous Message Pavel Stehule 2018-03-01 19:26:36 Re: TO_DATE Function unintended behavior when month value is greater than 12