Message-ID: <gh-pgjdbc-pgjdbc-1225@github.com>
From: "geekbeast (@geekbeast)" <noreply+geekbeast@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 26 Jun 2018 08:09:56 +0000
Subject: [pgjdbc/pgjdbc] issue #1225: Java 8 Time Support for Postgres Arrays
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Id: 3698721
X-GitHub-Author-Login: geekbeast
X-GitHub-Issue: 1225
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-State: open
X-GitHub-Type: issue
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/1225
Content-Type: text/plain; charset=utf-8

I've been looking around and it looks like Java 8 Time Support for Postgres Arrays is not yet implemented and there aren't any other issues so opening a new one.

At first glance it looks like the required change would be in ```PgArray.buildArray(...)``` as it currently defaults to marshalling DATE, TIME, and TIMESTAMP to java.sql.* classes.

Looking at the existing methods called by ```ResultSet.getObject(colName, Class<T>)``` its straightforward to get the value. What's not clear to me is (1) whether the binary case that is handled getObject needs to be handled for arrays and (2) how to maintain backward compatibility. One way to possibly support in a backwards compatible is to implement the version of getArray that takes a map.

For now, I'm manually doing the conversion as I'm on tight deadline and it's easy enough to do manual conversions.