Received: from laura.owlscreech.com (IDENT:root@[208.177.146.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6CGOgW97677 for ; Wed, 12 Jul 2000 12:24:43 -0400 (EDT) Received: from [208.177.146.11] (audrey.owlscreech.com [208.177.146.11]) by laura.owlscreech.com (8.9.3/8.8.7) with ESMTP id KAA25695 for ; Wed, 12 Jul 2000 10:24:35 -0600 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Wed, 12 Jul 2000 10:24:36 -0600 Subject: Bug in to_char() From: Brian Powell To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Archive-Number: 200007/131 Greetings, Working with PostGreSQL 7.02, I found the following problem: The AM/PM designator in the to_char function does not work proper for 13:00 and 12:00. See the following: test=> select to_char('3-12-2000 14:00'::timestamp, 'Dy, HH12:MI PM'); to_char --------------- Sun, 02:00 PM (1 row) This is correct. test=> select to_char('3-12-2000 8:00'::timestamp, 'Dy, HH12:MI PM'); to_char --------------- Sun, 08:00 AM (1 row) This is correct. test=> select to_char('3-12-2000 13:00'::timestamp, 'Dy, HH12:MI PM'); to_char --------------- Sun, 01:00 AM (1 row) NO! This is incorrect test=> select to_char('3-12-2000 1:00'::timestamp, 'Dy, HH12:MI PM'); to_char --------------- Sun, 01:00 AM (1 row) This is correctly 1 am. nicklebys=> select to_char('3-12-2000 12:00'::timestamp, 'Dy, HH12:MI PM'); to_char --------------- Sun, 12:00 AM (1 row) NO! This is 12:00 pm. 0:00 or 24:00 is 12:00 am. Any known work arounds or bug fixes planned? Thanks, Brian -- +-----------------------------------------------------------+ | Brian Powell, President brian@filogroup.com | | Filo Group www.filogroup.com | | One Broadway, Suite 300A AIM: filogroupbrian | | Denver, CO 80203 ICQ: 75037370 | | 303.733.3248 office 303.733.7122 fax | +-----------------------------------------------------------+