Re: timestamptz alias

Hi, Andrew,

Andrew Dunstan wrote:

>> It's not only about documenting the pure existence of the aliases (which
>> was already documented in the table on the datatype TOC page), it's also
>> about telling the user which of the names are the ones to avoid, and the
>> reasons to do so.
>
> *blink* Why do any need to be avoided? What you use is a matter of
> taste, and your organisation's coding standards. From a purely technical
> POV I don't see any reason to avoid using either the canonical type
> names or the various aliases.

At least compatibility with the SQL standard, as well as with other
Databases might be a reason.

Using pure "timestamp" may lead human readers to be confused, because it
has both meanings with and without timezone historically, this might be
a reason to prefer the "timestamp with[out] time zone" wording.

HTH,
Markus

--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org