Open pboguslawski opened 1 year ago
Schema object names after upgrading 6.0 LTS to 6.5 LTS identical with schema names in fresh 6.5 LTS installation.
After upgrading exiting 6.0.48 to 6.5.2 (source method), some FKs names was left unotuched in MariaDB (Debian 11):
KEY `FK_groups_create_by_id` (`create_by`), KEY `FK_groups_change_by_id` (`change_by`), KEY `FK_groups_valid_id_id` (`valid_id`), CONSTRAINT `FK_groups_change_by_id` FOREIGN KEY (`change_by`) REFERENCES `users` (`id`), CONSTRAINT `FK_groups_create_by_id` FOREIGN KEY (`create_by`) REFERENCES `users` (`id`), CONSTRAINT `FK_groups_valid_id_id` FOREIGN KEY (`valid_id`) REFERENCES `valid` (`id`)
Same objects have different name in fresh 6.5 install:
KEY `FK_permission_groups_create_by_id` (`create_by`), KEY `FK_permission_groups_change_by_id` (`change_by`), KEY `FK_permission_groups_valid_id_id` (`valid_id`), CONSTRAINT `FK_permission_groups_change_by_id` FOREIGN KEY (`change_by`) REFERENCES `users` (`id`), CONSTRAINT `FK_permission_groups_create_by_id` FOREIGN KEY (`create_by`) REFERENCES `users` (`id`), CONSTRAINT `FK_permission_groups_valid_id_id` FOREIGN KEY (`valid_id`) REFERENCES `valid` (`id`)
Environment
Expected behaviour
Schema object names after upgrading 6.0 LTS to 6.5 LTS identical with schema names in fresh 6.5 LTS installation.
Actual behaviour
After upgrading exiting 6.0.48 to 6.5.2 (source method), some FKs names was left unotuched in MariaDB (Debian 11):
Same objects have different name in fresh 6.5 install: