OK, so we have a bug. Thanks.
---------------------------------------------------------------------------
Chad Wagner wrote:
> On 2/3/07, Bruce Momjian <bruce@momjian.us> wrote:
> >
> >
> > Would someone please confirm that our behavior in the three queries
> > below matches Oracle's behavior?
>
>
> Here is output from Oracle:
>
> Connected to:
> Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
> With the Partitioning, OLAP and Data Mining options
>
> SQL> alter session set nls_timestamp_format = 'YYYY-MM-DD HH.MI.SSXFF AM';
>
> Session altered.
>
> SQL> select to_timestamp('January 2006', 'Month YYYY') from dual;
>
> TO_TIMESTAMP('JANUARY2006','MONTHYYYY')
> ---------------------------------------------------------------------------
> 2006-01-01 12.00.00.000000000 AM
>
> SQL> select to_timestamp('January 2006', 'Month YYYY') from dual;
>
> TO_TIMESTAMP('JANUARY2006','MONTHYYYY')
> ---------------------------------------------------------------------------
> 2006-01-01 12.00.00.000000000 AM
>
> SQL> select to_timestamp('January 2006', 'FMMonth YYYY') from dual;
>
> TO_TIMESTAMP('JANUARY2006','FMMONTHYYYY')
> ---------------------------------------------------------------------------
> 2006-01-01 12.00.00.000000000 AM
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
