Fix wrong constraint action on schema upgraded

Author: Rothes

bukkit/src/main/kotlin/io/github/rothes/esu/bukkit/module/chatantispam/user/CasDataManager.kt

@@ -51,8 +51,8 @@ object CasDataManager {
     init {
         transaction(database) {
             // <editor-fold desc="TableUpgrader">
-            TableUpgrader(ChatSpamTable, 2, {
-                println("Upgrading ChatSpamDataTable")
+            TableUpgrader(ChatSpamTable, 3, {
+                println("Upgrading ChatSpamDataTable to 2")
                 fun alter(column: String, type: String) {
                     exec("ALTER TABLE `$tableName` MODIFY COLUMN `$column` $type")
                 }
@@ -62,6 +62,10 @@ object CasDataManager {
                 alter("data", "TEXT NOT NULL COLLATE utf8mb4_bin")
                 exec("ALTER TABLE `$tableName` ADD CONSTRAINT `fk_chat_spam_data_user__id` FOREIGN KEY (`user`) REFERENCES `users` (`id`) ON UPDATE CASCADE ON DELETE NO ACTION")
                 exec("ALTER TABLE `$tableName` ADD CONSTRAINT `data` CHECK (json_valid(`data`))")
+            }, {
+                println("Upgrading ChatSpamDataTable to 3")
+                exec("ALTER TABLE `$tableName` DROP FOREIGN KEY `fk_chat_spam_data_user__id`")
+                exec("ALTER TABLE `$tableName` ADD CONSTRAINT `fk_chat_spam_data_user__id` FOREIGN KEY (`user`) REFERENCES `users` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE")
             })
             // </editor-fold>
             SchemaUtils.create(ChatSpamTable)