https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16170
Marcel de Rooy <m.de.r...@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #49707|0 |1 is obsolete| | Attachment #49708|0 |1 is obsolete| | --- Comment #6 from Marcel de Rooy <m.de.r...@rijksmuseum.nl> --- Created attachment 49723 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=49723&action=edit Bug 16170: Pseudo foreign key in Items While many of us would like to get rid of biblioitems one day, the current scheme includes a biblioitemnumber and a biblionumber in Items. (Which is not so great..) But also note that biblionumber is NOT defined as a foreign key in Items, although a belongs_to relation has been added to the DBIx scheme! This inconsistency should be resolved. The "remove biblioitem table" operation is a large one, but in the meantime we better make biblionumber a regular FK not a 'pseudo' one. Note: If in an (very) exceptional case biblionumbers are found in items, that do not exist in biblio, this patch prints a warning at upgrade time and does not add the constraint. @RM: Please update the DBIx scheme accordingly. Test plan: [1] Run the upgrade. Check if the FK constraint has been added. [2] Remove the FK constraint. Change the biblionumber of one item to an unexisting record. Run the upgrade again. Notice the warning. Signed-off-by: Marcel de Rooy <m.de.r...@rijksmuseum.nl> Tested both cases: constraint added as well as warning printed. Signed-off-by: Mark Tompsett <mtomp...@hotmail.com> -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/