| From: | George Woodring <george(dot)woodring(at)iglass(dot)net> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL solution for my JDBC timezone issue |
| Date: | 2015-02-24 15:36:20 |
| Message-ID: | CACi+J=QfZha4Ok8Zq5t1To8yKskYyd55M-+ok+8G_M0cdKLmQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
>
>
>
> So:
>
> JDBC Web servers(US/East) <---> 90 database (5 different timezones)
>
> Therefore everything to the end user is passed through the Web servers?
>
> Is there a reason why the databases have different timezones?
>
> Seems to me less complicated to have all the databases share the UTC
> timezone. Then you only have one offset, US/East <--> UTC.
>
>
We originally did it for simplicity sake, the database is set for our
customer's timezone. So when we grabbed a date from the db, it would in
the correct timezone for the viewer, without the web code having to know
the timezone.
George Woodring
iGLASS Networks
www.iglass.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2015-02-24 15:39:35 | Re: Sequences not moved to new tablespace |
| Previous Message | Tom Lane | 2015-02-24 15:32:42 | Re: Sequences not moved to new tablespace |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Flower | 2015-02-24 19:36:46 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Adrian Klaver | 2015-02-24 15:29:46 | Re: SQL solution for my JDBC timezone issue |