Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues
Date
Msg-id CA+0W9LN_57pd7UUr-nmQYfaPayeGT_Cqm8V-G2ycCtPSQHkVxw@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues  (Radosław Smogura <rsmogura@softperience.eu>)
Responses Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues  (Stefan Keller <sfkeller@gmail.com>)
List pgsql-jdbc
On 10 January 2012 06:57, Radosław Smogura <rsmogura@softperience.eu> wrote:

> In real world BLOBs are transfered as references, and those references are
> managed in way as the trigger does. Nacked PG doesn't support deletion, Oid is
> universal type so it can't be used by GC approach, unles collector will know
> which Oid is LOB oid.

So you just end up with a conservative collector, not an exact
collector. In practice conservative collectors work OK. (You can use a
subtype to identify OIDs-that-refer-to-a-LO as suggested elsewhere in
the thread if you want an exact collector)

Oliver

pgsql-jdbc by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues
Next
From: Joseph Shraibman
Date:
Subject: Re: problem: query result in jdbc is <> result in psql