Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 27A769FB388 for ; Wed, 4 Oct 2006 12:52:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 91945-05 for ; Wed, 4 Oct 2006 12:52:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id C0E3E9FB37B for ; Wed, 4 Oct 2006 12:52:19 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (p549D1602.dip0.t-ipconnect.de [84.157.22.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id E57CC65997 for ; Wed, 4 Oct 2006 17:54:44 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id E17A218818CDE for ; Wed, 4 Oct 2006 17:52:17 +0200 (CEST) Message-ID: <4523D8B1.7050007@logix-tt.com> Date: Wed, 04 Oct 2006 17:52:17 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.5 (X11/20060812) MIME-Version: 1.0 To: PostgreSQL-development hackers Subject: Re: timestamptz alias References: <45218F90.1050303@logix-tt.com> <794403F6-6CB5-4726-806C-5EF76D64C7E3@themactionfaction.com> <34B58049-42F3-468D-AA2A-AE79DC8FB244@decibel.org> <45222B63.2070608@logix-tt.com> <26117.1159889582@sss.pgh.pa.us> <452381C8.5090804@logix-tt.com> <4523C28F.4080404@dunslane.net> In-Reply-To: <4523C28F.4080404@dunslane.net> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigBC4A2BAE56182B32919F216D" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.204 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/229 X-Sequence-Number: 92126 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBC4A2BAE56182B32919F216D Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, Andrew, Andrew Dunstan wrote: >> It's not only about documenting the pure existence of the aliases (whi= ch >> was already documented in the table on the datatype TOC page), it's al= so >> about telling the user which of the names are the ones to avoid, and t= he >> 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 technica= l > 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 --=20 Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org --------------enigBC4A2BAE56182B32919F216D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFI9ixyHQIGEs7eeARA58iAKCPnH2fHsPHiZu+M95i6ORnoEIXrwCg32AM o5PzMEWP8wNc5mK9A5W2S5I= =Jcdw -----END PGP SIGNATURE----- --------------enigBC4A2BAE56182B32919F216D--