public inbox for [email protected]  

help / color / mirror / Atom feed
From: Markus Schaber <[email protected]>
To: PostgreSQL-development hackers <[email protected]>
Subject: Re: timestamptz alias
Date: Wed, 04 Oct 2006 17:52:17 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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



Attachments:

  [application/pgp-signature] signature.asc (252B, 2-signature.asc)
  download

view thread (18+ messages)  latest in thread

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: timestamptz alias
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox