Re: Documentation bug / oversight

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Documentation bug / oversight
Date: 2015-12-15 14:26:09
Message-ID: CADK3HHKPmrtVr_dYW1nn2gsTeMmqYuB-Vp2fCAJmrGHkrCCxNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Thanks, I'll have a look!

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

On 15 December 2015 at 02:52, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:

> The Postgres JDBC documentation regarding the use of setBinaryStream() for
> bytea columns states[1]:
>
> The length parameter to setBinaryStream must be correct. There is no
> way to indicate that the stream is of unknown length.
> If you are in this situation, you must read the stream yourself into
> temporary storage and determine the length.
>
>
> I think this is no longer correct. Build 1200 introduced the ability to do
> just that[2]:
>
> * Support for setBinaryStream with unknown length
> https://github.com/pgjdbc/pgjdbc/pull/220
>
> My tests have shown that setBinaryStream(int, InputStream) indeed works
> just fine (as expected from the release notes)
>
>
> Regards
> Thomas
>
>
> [1]
> https://jdbc.postgresql.org/documentation/94/binary-data.html#binary-data-example
> [2]
> https://jdbc.postgresql.org/documentation/changelog.html#version_9.4-1200
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Matthew Bellew 2015-12-15 15:49:52 Fwd: Re: timestampdiff() implementation
Previous Message Philippe Marschall 2015-12-15 08:40:19 Re: timestamp with time zone wire format