Serial Units won't go into Copy Buckets

[Mike Rylander]

While serial.unit is a child table of asset.copy, container.copy_bucket_item requires its target_copy column satisfy an FKEY constraint to asset.copy.id. So, trying to add a unit-cum-copy to a copy bucket results in an ugly error.

We can remove this constraint, but there is a CASCADE ON DELETE clause on the constraint that we'd lose.

Thoughts, other than ripping out serial.unit?

[Ben Shum (bshum)]

Marking confirmed and stating that Mike's idea in IRC to drop the constraint worked for us to allow serial units to be added to copy buckets.

Something like:

ALTER TABLE container.copy_bucket_item DROP CONSTRAINT copy_bucket_item_target_copy_fkey;

[Lebbeous Fogle-Weekley (lebbeous)]

If somebody can readily clarify for me, you'll save me the trouble of a test. With our triggers that just set deleted = true for copies instead of actually allowing them to be deleted for the most part, will that cascade on delete ever really be invoked? If not, then I suppose it's worth it to remove the FK constraint in this case.

[Galen Charlton (gmc)]

A patch for this is include in the overall branch for the web staff client's serial module; please see bug 1708291.

[Mike Rylander (mrylander)]

Fix from http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/fix_vii_inh_fkey pushed to master. Thanks, Galen!