From: | Peter Mount <petermount(at)maidstone(dot)gov(dot)uk> |
---|---|
To: | "'Ingo Luetkebohle'" <ingo(at)blank(dot)pages(dot)de>, Greg Speegle <Greg(at)10happythings(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | RE: jdbc: getBinaryStream blocks on second call |
Date: | 2000-12-05 14:44:33 |
Message-ID: | 1B3D5E532D18D311861A00600865478CF1B611@exchange1.nt.maidstone.gov.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hmm, I'm a tad worried now, as that's not how the driver should be behaving.
You shouldn't need to close the Connection just to read a Stream...
Peter
--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount(at)maidstone(dot)gov(dot)uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council
> -----Original Message-----
> From: Ingo Luetkebohle [mailto:ingo(at)blank(dot)pages(dot)de]
> Sent: Sunday, December 03, 2000 9:33 PM
> To: Greg Speegle
> Cc: pgsql-interfaces(at)postgresql(dot)org
> Subject: Re: [INTERFACES] jdbc: getBinaryStream blocks on second call
>
>
> On Sun, Dec 03, 2000 at 01:10:21PM -0600, Greg Speegle wrote:
> > If you have to read it twice, the only way to gaurantee that it
> > works, is to close the Statement and do it again.
>
> Thanks for the tip, it led me in the right direction. Closing the
> Statement didn't suffice, but closing the whole DB connection
> worked. Not beautiful, but ok for the moment.
>
> --
> Ingo Luetkebohle / ingo(at)blank(dot)pages(dot)de / 95428014
> /
> |PraxisXML Open Source contact; Computational Linguistics
> |student; Fargonauten.DE sysadmin; Gimp Registry (not-)maintainer;
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-12-05 14:55:21 | RE: jdbc7.0-1.2.jar |
Previous Message | Peter Mount | 2000-12-05 14:43:07 | RE: jdbc: getBinaryStream blocks on second call |