From: | Peter Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | Alejandro Alberola Arias <alberola(at)bio(dot)es> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OIDs and JDBC |
Date: | 2000-10-09 11:34:44 |
Message-ID: | Pine.LNX.4.21.0010091232400.772-100000@maidast.demon.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 6 Oct 2000, Alejandro Alberola Arias wrote:
> Hello,
>
> When I delete a row that contains a large object
> (better said an OID pointing to a large object) using
> JDBC, does this large object becomes orphan ?
> Must I remove manually the large object or is it
> remove automatically ?
Yes. This is because there is no actuall link between the row and the
BLOB.
In the source (src/contrib/lo) there is a simple example trigger that I
wrote some time ago, that you can associate with a table to monitor
DELETE and UPDATE operations, and if a field of type OID is affected, so
is the associated large object.
It's not perfect, but it works.
Peter
--
Peter T Mount peter(at)retep(dot)org(dot)uk http://www.retep.org.uk
PostgreSQL JDBC Driver http://www.retep.org.uk/postgres/
Java PDF Generator http://www.retep.org.uk/pdf/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-10-09 11:36:28 | Re: OID use |
Previous Message | Vilson farias | 2000-10-09 10:33:40 | Fw: Referencial integrity when there are timestamp primary keys |