From: Peter T Mount <peter@retep.org.uk>
To: xriley@encryptix.com
Cc: pgsql-interfaces@postgresql.org
Cc: xriley@encryptix.com
Subject: Re: Deleting a list of external xinv/xinx files using JDBC
Date: Tue, 16 Jan 2001 04:12:46 -0500 (EST)
Message-ID: <979636366.3a64108e75214@webmail.retep.org.uk> (raw)
In-Reply-To: <19016070071ED411B61300508BAC4B75915D6D@exch1etix.encryptix.com>
References: <19016070071ED411B61300508BAC4B75915D6D@exch1etix.encryptix.com>
Quoting xriley@encryptix.com:
> I'm using the JDBC setBytes to insert a list of large object blobs.
> The side-effect of this is two external files (xinvOID and xinxOID)
> for every blob inserted.
>
> If I use a JDBC delete sql statement to delete the records
> containing the blobs, the external xin* files are not deleted.
>
> Is this by design? If so, is there a work around for deleting
> a LIST of records AND the associated external blob file?
Yes this is by design (in the backend) as there is no real link between your
table and the blob. If you look under /contrib you will find ways of fixing
this using triggers that watch your table and when a row containing a blob is
deleted or the blob amended then the old blob is deleted in the background.
Peter
--
Peter Mount peter@retep.org.uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: peter@retep.org.uk, xriley@encryptix.com
Subject: Re: Deleting a list of external xinv/xinx files using JDBC
In-Reply-To: <979636366.3a64108e75214@webmail.retep.org.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox