Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Radosław Smogura <rsmogura(at)softperience(dot)eu>
Cc: Alban Hertroys <haramrae(at)gmail(dot)com>, Stefan Keller <sfkeller(at)gmail(dot)com>, pgsql-general List <pgsql-general(at)postgresql(dot)org>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues
Date: 2012-01-09 20:21:37
Message-ID: CA+0W9LN_57pd7UUr-nmQYfaPayeGT_Cqm8V-G2ycCtPSQHkVxw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-jdbc
On 10 January 2012 06:57, Radosław Smogura <rsmogura(at)softperience(dot)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

In response to

Responses

pgsql-jdbc by date

Next:From: Joseph ShraibmanDate: 2012-01-09 22:52:47
Subject: Re: problem: query result in jdbc is <> result in psql
Previous:From: Alban HertroysDate: 2012-01-09 19:31:38
Subject: Re: Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues

pgsql-general by date

Next:From: Andy ChambersDate: 2012-01-09 21:03:28
Subject: Update takes longer than expected
Previous:From: Scott MarloweDate: 2012-01-09 20:06:04
Subject: Re: queries timeout during backup postgres database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group