public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Nasby <[email protected]>
To: Markus Schaber <[email protected]>
Cc: PostgreSQL-development hackers <[email protected]>
Subject: Re: timestamptz alias
Date: Thu, 5 Oct 2006 21:18:40 -0500
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]>
	<[email protected]>

On Oct 4, 2006, at 10:52 AM, Markus Schaber wrote:
> 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.

It would be nice to denote types/aliases that are and aren't ANSI. A  
number are marked  in the docs, but it would be good to add the info  
to that summary table.
--
Jim Nasby                                            [email protected]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




--
Jim Nasby                                    [email protected]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

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], [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