https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27964
--- Comment #5 from Andreas Jonsson <[email protected]> --- I think it is hard to come up with a test plan for this issue. But it is obviously a problem that if several columns with the same name is included the resulting rows will not be well defined when fetched as hashes. I know that there is code that crashes when the subscriptionhistory entry is missing. This patch do not fix all problems, however. The real problem is that the database schema is flawed. The history table should, if designed according to normal database principles, contain one entry per historic number. But it seem to be designed to always contain exactly one entry that that enumerates the historic numbers in one attribute. However, deletes in the biblio table cascades to the subscriptionhistory table, so the subscriptionhistory entry can be missing. Note that the biblionumber in the history entry may be different from the biblionumber in the subscription. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
