[Koha-bugs] [Bug 1963] Problem with deleted biblio in a virtual shelf

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1963

--- Comment #6 from Frédéric Demians <frederic at tamil.fr> ---
Thanks a lot Paul for catching that!

Yes, there should have a constraint on shelfcontents.biblionumber field.
And there isn't one.

For others who would like to test there table:

  SHOW CREATE TABLE virtualshelfcontents

I have several Koha DB without constraints on that table, and on other
tables. This issue doesn't come from an updatedatabase.pl having failed,
but from tables which have been in the past associated with MyISAM
storage engine rather than InnoDB. MyISAM doesn't support referential
integrity constraints. So if a table was MyISAM during an update adding
a new constraint, the constraint was just not created. 

So, please, push this patch. The constraint issue is more general, and
related to storage Engine used. InnoDB is now mandatory. InnoDB is the
MySQL default storage engine since version 5.1, replacing MyISAM. So the
problem may occur less and less. But for legacy Koha DB, it can happen,
and it can have surprising effect like this bug.

-- 
You are receiving this mail because:
You are watching all bug changes.