RE: jdbc: getBinaryStream blocks on second call
От | Peter Mount |
---|---|
Тема | RE: jdbc: getBinaryStream blocks on second call |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B611@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответ на | jdbc: getBinaryStream blocks on second call (Ingo Luetkebohle <ingo@blank.pages.de>) |
Список | 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@maidstone.gov.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@blank.pages.de] > Sent: Sunday, December 03, 2000 9:33 PM > To: Greg Speegle > Cc: pgsql-interfaces@postgresql.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@blank.pages.de / 95428014 > / > |PraxisXML Open Source contact; Computational Linguistics > |student; Fargonauten.DE sysadmin; Gimp Registry (not-)maintainer; >
В списке pgsql-interfaces по дате отправления: