FW: OID, compatible=7.1 and getBinaryStream() in 7.4 driver + 7.4 database
От | Alexey Yudichev |
---|---|
Тема | FW: OID, compatible=7.1 and getBinaryStream() in 7.4 driver + 7.4 database |
Дата | |
Msg-id | 8BCBF9DB739F034B87FE7C7D30EAE55CEA573F@hqex2k.francoudi.com обсуждение исходный текст |
Ответы |
Re: FW: OID, compatible=7.1 and getBinaryStream() in 7.4
|
Список | 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@postgresql.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.4beta3) and from CVS (:pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot) and discovered that with compatible=7.1flag invoking rs.getBinaryStream() or rs.getBytes() on an OID column blocks forever (somewhere in java.net.SocketInputStreamso 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.2server 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 wantto make sure that this issue is a bug that is about to be fixed or something different. Thanks.
В списке pgsql-jdbc по дате отправления: