gitea
/
Koha-clms
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Bug 40517: (QA follow-up): Fix kohstructure.sql 

The order was wrong, PRIMARY KEY must come first.

Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
This commit is contained in:
Pedro Amorim 2025-10-24 16:59:28 +00:00 committed by Lucas Gass
parent 14d1c1338a
commit dc5cee850d
No known key found for this signature in database
GPG Key ID: 60B447398B0D36CA
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
installer/data/mysql/kohastructure.sql
View File

@ -3554,9 +3554,9 @@ CREATE TABLE `hold_groups` (
`hold_group_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`borrowernumber` int(11) DEFAULT NULL COMMENT 'foreign key, linking this to the borrowers table',
`visual_hold_group_id` int(11) DEFAULT NULL COMMENT 'visual ID for this hold group, in the context of the related patron',
PRIMARY KEY (`hold_group_id`),
KEY `hold_groups_borrowernumber` (`borrowernumber`),
CONSTRAINT `hold_groups_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE,
PRIMARY KEY (`hold_group_id`)
CONSTRAINT `hold_groups_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
/*!40101 SET character_set_client = @saved_cs_client */;