BUG #6241: JDBC: blob doesnot work with bytea

From: "Stefan Franke" <stefan(at)franke(dot)ms>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6241: JDBC: blob doesnot work with bytea
Date: 2011-10-06 08:26:51
Message-ID: 201110060826.p968Qpkl005684@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 6241
Logged by: Stefan Franke
Email address: stefan(at)franke(dot)ms
PostgreSQL version: 9.1
Operating system: any
Description: JDBC: blob doesnot work with bytea
Details:

To persist a blob you can also use bytea. Unfortunately the JDBC driver does
not support this.

Especially if you can't control the way how the column is accessed, e.g.
using JPA

@Lob
@Column(name = "DATA") // using bytea
private byte[] data;

it fails with distinct JPA implementations (e.g. Hibernate) since the JPA
layer tries to access it as blob.

My workaround is to patch the class org.postgresql.jdbc4.Jdbc4ResultSet:

public java.sql.Blob getBlob(int i) throws SQLException
{
checkResultSet(i);
if (wasNullFlag)
return null;

try {
return new Jdbc4Blob(connection, getLong(i));
} catch (PSQLException ex) {
// bytea use a dummy Blob
return new SerialBlob(getBytes(i));
}
}

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Cristian Cruz 2011-10-06 18:36:42 Re: BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)
Previous Message Daniel Cristian Cruz 2011-10-06 00:33:55 Re: BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)