| From: | pgsql-bugs(at)postgresql(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | no way in LargeObject API to detect short read? |
| Date: | 2000-11-14 06:58:56 |
| Message-ID: | 200011140658.eAE6wuj89143@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
Paul M. Aoki (aoki(at)acm(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2000-11-14 09:20:55 | Problems with rules |
| Previous Message | pgsql-bugs | 2000-11-14 06:45:31 | no meaningful way to determine fe or be version? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jos Antonio Matute Calvo | 2001-01-10 16:31:30 | jdbc driver: Support for 'BOOL' |
| Previous Message | Peter Mount | 2000-10-21 16:47:41 | Re: Re: JDBC Performance |