From: | Rob Nikander <rob(dot)nikander(at)gmail(dot)com> |
---|---|
To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: arrays of composite types, and client drivers like JDBC |
Date: | 2019-06-17 05:09:30 |
Message-ID: | 84936C57-A75C-4068-834C-1966C1034F89@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Jun 15, 2019, at 1:47 PM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
> Basically because java would have to create a type dynamically to parse the data into.
> There's nothing inherently difficult about parsing the data, the problem is what do we put it into ?
(I accidentally replied off-list, so resending this.)
It could parse it to strings and convert only when I call `getInt`, `getTimestamp`, etc. But, like you said, I see that the parsing isn't that difficult, so I wrote something that seems to work. Probably that code should be in the library, not my application. If I test this out some more and it still seems to work, I’ll ask again about contributing to https://github.com/pgjdbc/pgjdbc.
Rob
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Nikander | 2019-06-17 05:34:33 | Async client libraries - not worth it? |
Previous Message | Stephen Frost | 2019-06-16 21:31:17 | Re: checkpoints taking much longer than expected |