Comment 5 for bug 1772028

Hmmm, our database has this:

CONSTRAINT copy_pkey PRIMARY KEY (id),

in asset.copy.

In our 2.12 production database, the information_schema.referential_constraints has two rows with unique_constraint_name = copy_pkey. One with constraint_name = asset_copy_note_copy_fkey The other has constraint_name = import_item_imported_as_fkey

Those unique_constraint_name = copy_pkey rows are gone in our test databases that have been upgraded to 3.0 and 3.1.