Marcel de Rooy
33694a8faa
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.rooy@rijksmuseum.nl> Tested both cases: constraint added as well as warning printed. Signed-off-by: Mark Tompsett <mtompset@hotmail.com> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> |
||
---|---|---|
.. | ||
mysql |