Message-ID: <gh-pgjdbc-pgjdbc-1390-c698857550@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 25 Sep 2020 10:37:52 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #1390: LocalDateTime has invalid string serialization
In-Reply-To: <gh-pgjdbc-pgjdbc-1390@github.com>
References: <gh-pgjdbc-pgjdbc-1390@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 698857550
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 1390
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/1390#issuecomment-698857550
Content-Type: text/plain; charset=utf-8

Well as you aptly pointed out the JDBC spec doesn't contemplate both a timestamp with and without a TZ so ultimately we end up getting it right *most* of the time and wrong sometimes. If I changed it to the behaviour you wanted I would undoubtedly get another issue from someone wanting the behaviour the way it is right now. Timezones are an abomination...