Fix migration for vrpLogs_ChatReceivers

The FK was incorrect `vrpLogs_chat` vs `vrpLogs_Chat` which causes issues on linux (which is case sensitive). Issue #1
eXo-OpenSource · Jul 7, 2023 · 5f0225a · 5f0225a
1 parent fecf235
commit 5f0225a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/vrp/tables.sql b/vrp/tables.sql
@@ -210,7 +210,7 @@ CREATE TABLE IF NOT EXISTS `vrpLogs_ChatReceivers` (
   PRIMARY KEY (`MessageId`,`Receiver`) USING BTREE,
   KEY `vrpLogs_ChatReceivers_vrpLogs_Chat_ID_fk` (`MessageId`) USING BTREE,
   KEY `Receiver` (`Receiver`) USING BTREE,
-  CONSTRAINT `vrpLogs_ChatReceivers_vrpLogs_Chat_ID_fk` FOREIGN KEY (`MessageId`) REFERENCES `vrpLogs_chat` (`ID`)
+  CONSTRAINT `vrpLogs_ChatReceivers_vrpLogs_Chat_ID_fk` FOREIGN KEY (`MessageId`) REFERENCES `vrpLogs_Chat` (`ID`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3;