I suggest an extension to the standard since the syntax for <interval primary> is a bit awkward (and far beyond the ability to numerous application programmers)
<time zone> ::= AT <time zone specifier>
<time zone specifier> ::=
LOCAL
| TIME ZONE <interval primary>
| TIME ZONE <time zone offset>
| UTC
where <time zone offset> is a 5-character string with a sign and 4
digits in the form HHMM to specify the offset. Thus
SELECT ts AT TIME ZONE '-0700' FROM table;
and
SELECT ts AT UTC FROM table;
would both be valid statements.
Alternatively, if we don't want to introduce UTC as a key word, we
could allow <time zone offset> to have the value 'Z' or 'UTC'.
I don't think we should allow values as 'CET', 'MST' etc since there
are no precise standard which defines these.
--
Bernt Marius Johnsen, Staff Engineer
Database Technology Group, Sun Microsystems, Trondheim, Norway
signature.asc
Description: Digital signature
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
