On Wed, 7 Jan 2004, Martin Holz wrote:
> Hello,
>
> org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> in postgresql 7.4.1 wrongly assumes, that
> java.io.InputStream.read(byte[] b,int offset,int len )
> will always read len bytes. InputStream only guarantees to
> return at least 1
On Fri, 9 Jan 2004, Jonathan Purvis wrote:
> The JDBC driver that ships with PostgreSQL 7.4.1 doesn't insert floats
> of value NaN. As it uses Float.toString(x) to convert the value for
> insertion into the database, it tries to insert NaN instead of 'NaN' and
> gets the error "Attribute 'nan'
On Friday 09 January 2004 09:46, Kris Jurka wrote:
> On Wed, 7 Jan 2004, Martin Holz wrote:
> > Hello,
> >
> > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > in postgresql 7.4.1 wrongly assumes, that
> > java.io.InputStream.read(byte[] b,int offset,int len )
> > will always read
On Friday 09 January 2004 09:46, Kris Jurka wrote:
> On Wed, 7 Jan 2004, Martin Holz wrote:
> > Hello,
> >
> > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > in postgresql 7.4.1 wrongly assumes, that
> > java.io.InputStream.read(byte[] b,int offset,int len )
> > will always read
On Fri, 9 Jan 2004, Martin Holz wrote:
> On Friday 09 January 2004 09:46, Kris Jurka wrote:
>
> > The odd thing about the javadocs is that they say "The data will be
> > read from the stream as needed until end-of-file is reached." The
> > length parameter's comment is "the number of bytes in t
On Friday 09 January 2004 17:18, Kris Jurka wrote:
> I was referring to the documentation for setBinaryStream. You
> mentioned that it should throw an Exception if it couldn't read
> "length" bytes from the stream. I was commenting that our
> implementation might be wrong by checking the length
unsubscribe
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
