Message-ID: <gh-pgjdbc-pgjdbc-2311-c952896423@github.com>
From: "riba2101 (@riba2101)" <noreply+riba2101@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 27 Oct 2021 12:53:47 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2311: Why is client time zone not configurable?
In-Reply-To: <gh-pgjdbc-pgjdbc-2311@github.com>
References: <gh-pgjdbc-pgjdbc-2311@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: riba2101
X-GitHub-Comment-Id: 952896423
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2311
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-952896423
Content-Type: text/plain; charset=utf-8

yeah i kinda think we misunderstood each other.
to change the type on the DB is impossible at this moment. 

my proposal was to have an optional flag for the timezone in the connection string. i kinda fail to understand how this would break anything?

this is the case with the dates being converted into wrong zones when fetched(even as `Timestamp`)

in addition to that i found an deeper problem in psql itself.


`interval +336:00:00` what the driver converts a `Duration` into is DST aware, but `interval + 2 weeks` isn't