On Wed, 7 Jan 2004, Martin Holz wrote:
> in postgresql 7.4.1 wrongly assumes, that
> java.io.InputStream.read(byte b,int offset,int len )
> will always read len bytes. InputStream only guarantees to
> return at least 1 byte per call. The attached patch solves the bug.
Yes, it can even return 0 bytes if it feels like it.
> Btw. setBinaryStream() should really throw an SQLException, if
> in can not read as many bytes as expected from the InputStream.
> Otherwise the application might silently loss data.
The odd thing about the javadocs is that they say "The data will be read
from the stream as needed until end-of-file is reached." The length
parameter's comment is "the number of bytes in the stream."
This is strange because it seems to imply that the length argument is just
for informational purposes and should not be used to limit the amount of
data actually read from the stream.
In response to
pgsql-bugs by date
|Next:||From: Kris Jurka||Date: 2004-01-09 09:30:12|
|Subject: Re: JDBC driver doesn't handle NaN values|
|Previous:||From: Denis N. Stepanov||Date: 2004-01-09 06:10:46|
|Subject: Re: BUG #1044: snprintf() shipped with PostgreSQL is not|
pgsql-jdbc by date
|Next:||From: Antonio Gallardo||Date: 2004-01-09 09:17:53|
|Subject: Re: [BUG] - Invalid UNICODE character sequence found |
|Previous:||From: Kris Jurka||Date: 2004-01-09 08:33:02|
|Subject: Re: [BUG] - Invalid UNICODE character sequence found (0xc000)|