Thread
-
Bug report
Phil Rutschman <machack@rsnsoft.com> — 1999-10-05T02:48:02Z
============================================================================ POSTGRESQL BUG REPORT TEMPLATE ============================================================================ Your name : Phil Rutschman Your email address : machack@rsnsoft.com System Configuration --------------------- Architecture (example: Intel Pentium) : Intel Celeron Operating System (example: Linux 2.0.26 ELF) : Linux 2.3.18 ELF PostgreSQL version (example: PostgreSQL-6.5.1): PostgreSQL-6.5.1 Compiler used (example: gcc 2.8.0) : egcs-2.91.66 Please enter a FULL description of your problem: ------------------------------------------------ Dates including both a timezone offset and a timezone identifier fail parse as invalid dates. Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- select datetime('Sat, 2 Oct 1999 01:29:48 -0700 (MST)'::text) from some_table; ERROR: Bad datetime external representation although both of the following work: select datetime('Sat, 2 Oct 1999 01:29:48 -0700'::text) from some_table; select datetime('Sat, 2 Oct 1999 01:29:48 (MST)'::text) from some_table; If you know how this problem might be fixed, list the solution below: --------------------------------------------------------------------- As long as the supplied offset and timezone identifier are consistent, there seems no reason not to allow both. ---------------------------------------------------------------------- | Phil Rutschman Math & CS Major, Western Washington Univ. | | mailto:machack@rsnsoft.com http://www.rsnsoft.com/~machack/ | ---------------------------------------------------------------------- Miranda paused at the antibacterial soap. Would using it create a more resilient strain of bacteria? Should she chance it, endangering the free world, or just wipe the cheetos dust on her jeans?