From: | thomas(at)postgresql(dot)org |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src backend/parser/analyze.c backend/par ... |
Date: | 2001-10-03 05:29:27 |
Message-ID: | 200110030529.f935TRc36058@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql
Changes by: thomas(at)postgresql(dot)org 01/10/03 01:29:27
Modified files:
src/backend/parser: analyze.c gram.y parse_coerce.c
src/backend/utils/adt: date.c datetime.c numeric.c timestamp.c
varchar.c
src/include/catalog: catversion.h pg_proc.h
src/include/utils: date.h timestamp.h
src/test/regress/expected: horology.out time.out timestamp.out
timestamptz.out timetz.out
src/test/regress/sql: horology.sql time.sql timestamp.sql
timestamptz.sql timetz.sql
Log message:
Implement precision support for timestamp and time, both with and without
time zones.
SQL99 spec requires a default of zero (round to seconds) which is set
in gram.y as typmod is set in the parse tree. We *could* change to a
default of either 6 (for internal compatibility with previous versions)
or 2 (for external compatibility with previous versions).
Evaluate entries in pg_proc wrt the iscachable attribute for timestamp and
other date/time types. Try to recognize cases where side effects like the
current time zone setting may have an effect on results to decide whether
something is cachable or not.
From | Date | Subject | |
---|---|---|---|
Next Message | vev | 2001-10-03 10:35:37 | [WEBMASTER] 'www/html/bugs bugs.php' |
Previous Message | thomas | 2001-10-03 05:24:22 | pgsql/doc/src/sgml datatype.sgml |