X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E2C2C55112 for ; Fri, 4 Mar 2005 15:20:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 93310-01 for ; Fri, 4 Mar 2005 15:20:51 +0000 (GMT) Received: from www.onnet.cc (unknown [204.31.68.132]) by svr1.postgresql.org (Postfix) with ESMTP id A6D46550E6 for ; Fri, 4 Mar 2005 15:20:49 +0000 (GMT) Received: from 192.168.0.3 by www.onnet.cc (Sambar SMTPD); id s20050304082024.7275; Fri, 04 Mar 2005 08:20:24 Message-ID: <42287CB8.7040600@kensystem.com> Date: Fri, 04 Mar 2005 08:20:24 -0700 From: Ken Johanson User-Agent: Mozilla Thunderbird 1.0 (Windows/20050131) X-Accept-Language: en-us, en MIME-Version: 1.0 To: andrew@supernews.com Cc: pgsql-sql@postgresql.org Subject: Re: definative way to place secs from epoc into timestamp 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> <1109915231.28180.182.camel@bretsony> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.129 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/60 X-Sequence-Number: 20539 >>and the fact that I want the same value from the data base that I put >>into it. > > > "same" in which sense? The same absolute point in time? Or the same point > on a calendar? Obviously if the timezone doesn't change, then the two are > equivalent; but which one is your application actually looking for? (If > your app is using Unix epoch times, then it's looking only at the absolute > time and not the calendar time...) > 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