Re: to_timestamp error handling.

FYI, this behavior now returns:

	test=> select to_timestamp('20096010','YYYYMMDD');
	      to_timestamp
	------------------------
	 2013-12-18 00:00:00-05
	(1 row)

which doesn't have the :30 but is still odd.  I don't see any value
checking in to_timestamp.

---------------------------------------------------------------------------

Dhaval Jaiswal wrote:
> Hi All,
> 
> 
> 
> postgres=# select to_timestamp('20096010','YYYYMMDD');
> 
>        to_timestamp
> 
> ---------------------------
> 
>  2013-12-18 00:00:00+05:30
> 
> (1 row)
> 
> 
> 
> The month is 60 in my case and it is giving some random value, whereas I am
> expecting some error message like date is not valid.
> 
> 
> 
> Is it an expected behaviour?
> 
> 
> -- 
> Thanks & Regards,
> Dhaval Jaiswal
> EnterpriseDB
> Contact: 732-331-1300 Ext- 2022
> +91-20-30589 516 / 494
> web: www.enterprisedb.com

-- 
  Bruce Momjian          http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +