FW: OID, compatible=7.1 and getBinaryStream() in 7.4 driver + 7.4 database

From: "Alexey Yudichev" <Alexey(at)francoudi(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: FW: OID, compatible=7.1 and getBinaryStream() in 7.4 driver + 7.4 database
Date: 2003-12-16 09:40:37
Message-ID: 8BCBF9DB739F034B87FE7C7D30EAE55CEA573F@hqex2k.francoudi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Can I have any comments on this?

-----Original Message-----
From: Alexey Yudichev
Sent: Wednesday, December 10, 2003 12:17 PM
To: pgsql-jdbc(at)postgresql(dot)org
Subject: [JDBC] OID, compatible=7.1 and getBinaryStream() in 7.4 driver
+ 7.4 database

I have noticed that I can use only latest 7.4 driver with 7.4 database. I tried both driver from jdbc.postgresql.org (7.4 beta3) and from CVS (:pserver:anoncvs(at)anoncvs(dot)postgresql(dot)org:/projects/cvsroot) and discovered that with compatible=7.1 flag invoking rs.getBinaryStream() or rs.getBytes() on an OID column blocks forever (somewhere in java.net.SocketInputStream so I guess it's a server that is not responding). According to 7.4 documentation http://www.postgresql.org/docs/current/static/jdbc-binary-data.html, this should work. getBLOB() works great, but JBoss 3.2 server which I am using is only capable of dealing with large objects via getBinaryStream()/setBinaryStream().

Combination "OID, compatible=7.1 and getBinaryStream()" worked well in PostgreSQL 7.2 with latest 7.3 driver.

What options do I have? I could migrate to bytea although I don't liked the performance of it. But before I do that I want to make sure that this issue is a bug that is about to be fixed or something different.
Thanks.

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Germán Gazzoni 2003-12-16 12:06:03 REMOVE
Previous Message John Sidney-Woollett 2003-12-16 08:09:34 Re: Regarding install pgsql with JDBC support