Paul M. Aoki ([EMAIL PROTECTED]) 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
