Date: Wed, 12 Feb 2014 07:29:56 -0800 (PST)
From: rawi <only4com@web.de>
To: pgsql-sql@postgresql.org
Message-ID: <1392218996355-5791602.post@n5.nabble.com>
In-Reply-To: <52FB8D48.6010805@gmail.com>
References: <1392105285704-5791371.post@n5.nabble.com>
 <52FA3499.3020604@gmail.com> <1392193455856-5791556.post@n5.nabble.com>
 <52FB8D48.6010805@gmail.com>
Subject: Re: Time AT TIME ZONE: false result using offset instead of time
 zone name
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Adrian Klaver-3 wrote
> Welcome to the wacky world of time, it is all relative:) The choices are 
> handle everything as UTC until you present to the end user or use actual 
> timezones, for example, America/Los_Angeles. To illustrate, in your 
> original post you said:
> 
> "But it would be easier to ask a specific time offset (got from a client
> around the world), so for me +01 hour"
> 
> Do you know if that offset supplied by the client was POSIX or ISO in 
> its sign?

The (playing) question was: how would I get the time zone of a browser
somewhere unknown on earth?

And the found javascript solution would return the difference between GMT
and localtime in minutes, so for me west from Greenwich a negative integer.

Please save the following in a html file eg. "time_offset.html" and load it
in your browser:


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Time-AT-TIME-ZONE-false-result-using-offset-instead-of-time-zone-name-tp5791371p5791602.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql