> 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 Mount peter(at)retep(dot)org(dot)uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
In response to
pgsql-interfaces by date
|Next:||From: Michael Stephenson||Date: 2001-01-16 09:43:02|
|Subject: Re: Patch for JDBC timestamp problems|
|Previous:||From: Dave Page||Date: 2001-01-16 08:25:36|
|Subject: RE: ODBC and COPY |