Re: SQL solution for my JDBC timezone issue - Mailing list pgsql-general

From Adrian Klaver
Subject Re: SQL solution for my JDBC timezone issue
Date
Msg-id 54EB8DA8.6060302@aklaver.com
Whole thread Raw
In response to Re: SQL solution for my JDBC timezone issue  (George Woodring <george.woodring@iglass.net>)
Responses Re: SQL solution for my JDBC timezone issue  (Dave Cramer <pg@fastcrypt.com>)
Re: SQL solution for my JDBC timezone issue  (George Woodring <george.woodring@iglass.net>)
List pgsql-general
On 02/23/2015 12:15 PM, George Woodring wrote:
> This is what I was looking for, however the JDBC does something to make
> its timezone the default.
>
> My cluster is set to GMT, I have a DB that is set to US/Pacific,  when I
> get the connection from JDBC it is US/Eastern.  The reset command does
> not affect it.  I can set timezone in the code to 'US/Pacific" and I see
> it change, when I do another RESET timezone it goes back to US/Eastern.

In your original post you mentioned that access to the databases is
through a Web server.

Is there just one Web server with one time zone?

>
> Thanks,
> George Woodring
>
> iGLASS Networks
> www.iglass.net <http://www.iglass.net>
>
> On Mon, Feb 23, 2015 at 10:49 AM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>     George Woodring <george.woodring@iglass.net
>     <mailto:george.woodring@iglass.net>> writes:
>     > Yes, that is where we think we are heading, the issue is that the code does
>     > not know what it needs to be set back to.  We have 90 databases with 5
>     > different time zones.  I was just hoping for a more elegant solution than
>     > writing a lookup table that says if you are connecting to db x then set to
>     > timezone y.
>
>     "RESET timezone" ?
>
>                              regards, tom lane
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: George Woodring
Date:
Subject: Re: SQL solution for my JDBC timezone issue
Next
From: Dave Cramer
Date:
Subject: Re: SQL solution for my JDBC timezone issue