Received: from mail.crysberg.dk (square.crysberg.dk [194.192.196.2]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2F7c4x64916 for ; Thu, 15 Mar 2001 02:38:04 -0500 (EST) (envelope-from leif@danmos.dk) Received: from crysberg.dk (root@samba.crysberg.dk [192.168.10.12]) by mail.crysberg.dk (8.8.5/8.8.5) with ESMTP id IAA13203 for ; Thu, 15 Mar 2001 08:37:06 +0100 From: leif@danmos.dk Received: from danmos.dk (cdslj.crysberg.dk [192.168.10.20]) by crysberg.dk (8.10.2/8.8.7) with SMTP id f2F7bQl13172 for ; Thu, 15 Mar 2001 08:37:26 +0100 Date: Thu, 15 Mar 2001 08:37:26 +0100 Message-Id: <200103150737.f2F7bQl13172@crysberg.dk> To: pgsql-interfaces@postgresql.org Subject: to_date problem Content-Type: text X-Archive-Number: 200103/128 X-Sequence-Number: 1289 Hello, I have just observed the following problem: ------------------------------------------------------------------- testdb=# select to_date('2001-3-5 10:00', 'YYYY-MM-DD HH24:MI') from dual; to_date ------------ 2001-03-10 (1 row) testdb=# \q [nsadmin@ljserv calendar]$ psql --version psql (PostgreSQL) 7.1beta3 contains readline, history support Portions Copyright (c) 1996-2000, PostgreSQL, Inc Portions Copyright (c) 1996 Regents of the University of California Read the file COPYRIGHT or use the command \copyright to see the usage and distribution terms. ------------------------------------------------------------------- I know that the date constant is not in the same format as the format string, but shouldn't it be an error rather than 'just' returning a wrong date? Any suggestions, Leif (leif@danmos.dk)