Set NULLS NOT DISTINCT on constraint of database-backed app commands cache key

Fixes it always updating, since a `null` guild ID is used for global commands, and it was always distinct, meaning it never triggered the UNIQUE constraint, thus always creating a new entry in some cases

Author: freya022

BotCommands-core/src/main/kotlin/io/github/freya022/botcommands/internal/core/db/DatabaseImpl.kt

@@ -22,7 +22,7 @@ import java.sql.Connection
 import kotlin.time.toKotlinDuration
 
 // If the build script has 3.0.0-alpha.5_DEV, use the next release version, in this case 3.0.0-alpha.6
-private const val latestVersion = "3.0.0-beta.1" // Change in the latest migration script too
+private const val latestVersion = "3.0.0-beta.9" // Change in the latest migration script too
 
 private val logger = KotlinLogging.logger { }
 
@@ -147,4 +147,4 @@ internal class DatabaseImpl internal constructor(
 
         return compatibleFactories.first()
     }
-}
+}

BotCommands-core/src/main/resources/bc_database_scripts/V3.0.0.2026.02.15__Fix_global_application_commands_cache.sql

@@ -0,0 +1,16 @@
+------------------------------------------------------ 9th migration script for BotCommands ------------------------------------------------------
+---------------------------------- Make sure to run the previous scripts (chronological order) before this one -----------------------------------
+
+SET SCHEMA 'bc';
+
+UPDATE bc_version
+SET version = '3.0.0-beta.9'
+WHERE one_row = true;
+
+ALTER TABLE application_commands_cache
+    DROP CONSTRAINT application_commands_cache_application_id_guild_id_key;
+
+TRUNCATE application_commands_cache;
+
+ALTER TABLE application_commands_cache
+    ADD UNIQUE NULLS NOT DISTINCT (application_id, guild_id);