From: Ken Johanson <pg-user@kensystem.com>
To: pgsql-sql@postgresql.org
Cc: andrew@supernews.com
Subject: Re: definative way to place secs from epoc into timestamp
Date: Fri, 04 Mar 2005 08:29:09 -0700
Message-ID: <42287EC5.8090301@kensystem.com> (raw)
In-Reply-To: <42287CB8.7040600@kensystem.com>
References: <1109780719.28180.86.camel@bretsony>
<13089.1109793126@sss.pgh.pa.us>
<1109794066.27857.100.camel@bretsony>
<13466.1109795186@sss.pgh.pa.us>
<1109828560.27905.137.camel@bretsony>
<2bf00b6e6300e2c76bc3c09fa89e7913@myrealbox.com>
<1109834845.27905.147.camel@bretsony>
<slrnd2euj5.29om.andrew+nonews@trinity.supernews.net>
<1109915231.28180.182.camel@bretsony>
<slrnd2g2nm.29om.andrew+nonews@trinity.supernews.net>
<42287CB8.7040600@kensystem.com>
>
> Unix time stamps, short (int) or long res, are always supposed to GMT
> based, as far as I know - I never seen anything different, except maybe
> in homebrew software. So it should be both calendar and P.I.T. And you
> wouldn't need the TZ storage if the date-number and number-> translation
> itself takes the TZ arg so that it can localize the Human String for you.
>
> Ken
>
In fact, I would suggest that if there is any function, or field, that
takes a TZ-less argument (*especially* if it takes only the number),
that its name should be made to contain 'UTC' so clearly disambiguate
whats its intended use for (since zone-less values/fields SHOULD be
regarded as UTC) - Otherwise, some users will place epoch numbers
adjusted for the their timezone in the field (and even with daylight
saving offsets applies, somewhat amusingly but wrong). So then two
different users are using the exact same datatype for inconsistent
types. (just a concern for interoperability, user awareness, and when
an employee comes on-board and has to deal with bad legacy)
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: pgsql-sql@postgresql.org
Cc: pg-user@kensystem.com, andrew@supernews.com
Subject: Re: definative way to place secs from epoc into timestamp
In-Reply-To: <42287EC5.8090301@kensystem.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox