| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Cc: | George Woodring <george(dot)woodring(at)iglass(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] SQL solution for my JDBC timezone issue |
| Date: | 2015-02-23 16:57:47 |
| Message-ID: | CADK3HHJ5UzECZHuTxOk-jT4G0Fuufrct5CV1Liv1ca052BHJ2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
For posterity please be aware this will very likely break any timestamps
transfer using JDBC and binary transfer.
This is not recommended for general consumption
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On 23 February 2015 at 10:49, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> George Woodring <george(dot)woodring(at)iglass(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Drolet | 2015-02-23 18:08:57 | Sequences not moved to new tablespace |
| Previous Message | Alvaro Herrera | 2015-02-23 16:40:07 | Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Woodring | 2015-02-23 20:15:57 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Tom Lane | 2015-02-23 15:49:53 | Re: SQL solution for my JDBC timezone issue |