https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34355 --- Comment #132 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Katrin Fischer from comment #131)
I am currently validating that an updated database will have the same structure as a new installation. There is some difference caused by these patches:
@@ -4503,6 +4544,8 @@ CREATE TABLE `marc_order_accounts` ( `match_field` varchar(10) DEFAULT NULL COMMENT 'the field that a vendor account has been mapped to in a marc record', `match_value` varchar(50) DEFAULT NULL COMMENT 'the value to be matched against the marc record', PRIMARY KEY (`id`), + KEY `marc_ordering_account_ibfk_1` (`vendor_id`), + KEY `marc_ordering_account_ibfk_2` (`budget_id`), CONSTRAINT `marc_ordering_account_ibfk_1` FOREIGN KEY (`vendor_id`) REFERENCES `aqbooksellers` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `marc_ordering_account_ibfk_2` FOREIGN KEY (`budget_id`) REFERENCES `aqbudgets` (`budget_id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; @@ -4831,6 +4874,25 @@ CREATE TABLE `need_merge_authorities` ( ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */;
I am not sure about these keys here, please verify.
We came to the conflusion that this difference is harmless due to how the dump works vs the database update. -- You are receiving this mail because: You are watching all bug changes.