Message-ID: <gh-pgjdbc-pgjdbc-1390-c455626262@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 18 Jan 2019 17:32:19 +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: vlsi
X-GitHub-Comment-Id: 455626262
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-455626262
Content-Type: text/plain; charset=utf-8

>Tethering it to a time zone on insertion can (and does!) cause changes to the inserted time which are then apparent during retrieval.

@kdubb , would you please provide a test case with expected/actual output?