From: | rawi <only4com(at)web(dot)de> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Time AT TIME ZONE: false result using offset instead of time zone name |
Date: | 2014-02-12 15:29:56 |
Message-ID: | 1392218996355-5791602.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-02-12 16:30:16 | Re: Re: Time AT TIME ZONE: false result using offset instead of time zone name |
Previous Message | Adrian Klaver | 2014-02-12 15:03:36 | Re: Re: Time AT TIME ZONE: false result using offset instead of time zone name |