| From: | Tom Dunstan <pgsql(at)tomd(dot)cc> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Reading and writing off-heap data |
| Date: | 2017-09-25 08:06:01 |
| Message-ID: | CAPPfruwS_2K7X9h4Cz-zGwxdAv8Z4A_0C6eU1qbDAiGK1-UznQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
(Sorry, re-sending from address that is subscribed to the list)
On 22 September 2017 at 01:35, Vladimir Sitnikov <
sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> >I've submitted a PR [3] that introduces a Tuple class as a wrapper to
> pass around, which then allows us to do more interesting things with the
> data.
>
> I wonder how would you wire things since "new Tuple" is created before
> "new ResultSet", so it would be not that trivial to call user code (enable
> user to read bytes off the wire) from there.
>
Code affecting where incoming data goes would have to be registered with
the statement object or similar before execution.
Cheers
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2017-09-25 08:13:07 | Re: Timestamp parameter gets sent as date |
| Previous Message | Tom Dunstan | 2017-09-25 08:04:43 | Re: Reading and writing off-heap data |