Re: [JDBC] no way in LargeObject API to detect short read? - Mailing list pgsql-bugs

From Peter Mount
Subject Re: [JDBC] no way in LargeObject API to detect short read?
Date
Msg-id 5.0.2.1.0.20010130233100.00a21860@mail.retep.org.uk
Whole thread Raw
In response to no way in LargeObject API to detect short read?  (pgsql-bugs@postgresql.org)
List pgsql-bugs
At 01:58 14/11/00 -0500, pgsql-bugs@postgresql.org wrote:
>Paul M. Aoki (aoki@acm.org) reports a bug with a severity of 3
>The lower the number the more severe it is.
>
>Short Description
>no way in LargeObject API to detect short read?
>
>Long Description
>org.postgresql.largeobject.LargeObject.read(byte[],int,int) returns void
>instead of int.  there's therefore no reliable, non-exceptional way to
>detect short reads.
>
>the natural way to write blocked-read loops would be to assume that
>read(byte[],int,int) returned the number of bytes read or (e.g.) -1 on EOF.
>
>Sample Code
>
>
>No file was uploaded with this report

This method now returns the number of bytes read. It will be in CVS by
0900GMT tomorrow.

Peter

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: select fails on indexed varchars.
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: cannot index functions with multiple arguments