Thanks Mike. That's easy then. Bear with me...
What happens to rows in other tables? - The "label" field will match in asset.call_number is the call number - asset.copy contains the barcode - metabib.full has marc field info. (Is this index that will get rebuilt?) -- F. Grant Johnson Systems Coordinator Robertson Library University of Prince Edward Island >>> On 2008/10/16 at 9:04 PM, in message <[EMAIL PROTECTED]>, "Mike Rylander" <[EMAIL PROTECTED]> wrote: > On Thu, Oct 16, 2008 at 2:27 PM, Grant Johnson <[EMAIL PROTECTED]> wrote: >> I take it that it is not as easy as deleting rows from the > biblio.record_entry table!?! > > It is that easy. However, to /really/ delete them you'll need to drop > (and later reapply) the rule protecting against true deletes on that > table: > > BEGIN; > DROP RULE protect_bib_rec_delete ON biblio.record_entry; > -- > -- ... delete some records ... > -- > CREATE RULE protect_bib_rec_delete AS ON DELETE TO biblio.record_entry > DO INSTEAD UPDATE biblio.record_entry SET deleted = TRUE WHERE OLD.id > = biblio. > record_entry.id; > COMMIT;
