bug: fix issue with duplicate maps being selected during the veto process

Author: lukepolo

hasura/migrations/default/1761617285280_alter_table_public_match_map_veto_picks_add_unique_match_id_map_id/down.sql

@@ -0,0 +1 @@
+alter table "public"."match_map_veto_picks" drop constraint "match_map_veto_picks_match_id_map_id_key";

hasura/migrations/default/1761617285280_alter_table_public_match_map_veto_picks_add_unique_match_id_map_id/up.sql

@@ -0,0 +1,17 @@
+WITH duplicates AS (
+  SELECT 
+    id,
+    ROW_NUMBER() OVER (
+      PARTITION BY match_id, map_id 
+      ORDER BY created_at ASC, id ASC
+    ) as row_num
+  FROM match_map_veto_picks
+)
+DELETE FROM match_map_veto_picks 
+WHERE id IN (
+  SELECT id 
+  FROM duplicates 
+  WHERE row_num > 1
+);
+
+alter table "public"."match_map_veto_picks" add constraint "match_map_veto_picks_match_id_map_id_key" unique ("match_id", "map_id");

hasura/migrations/default/1761617297952_alter_table_public_match_region_veto_picks_add_unique_match_id_region/down.sql

@@ -0,0 +1 @@
+alter table "public"."match_region_veto_picks" drop constraint "match_region_veto_picks_match_id_region_key";

hasura/migrations/default/1761617297952_alter_table_public_match_region_veto_picks_add_unique_match_id_region/up.sql

@@ -0,0 +1,17 @@
+WITH duplicates AS (
+  SELECT 
+    id,
+    ROW_NUMBER() OVER (
+      PARTITION BY match_id, region 
+      ORDER BY created_at ASC, id ASC
+    ) as row_num
+  FROM match_region_veto_picks
+)
+DELETE FROM match_region_veto_picks 
+WHERE id IN (
+  SELECT id 
+  FROM duplicates 
+  WHERE row_num > 1
+);
+
+alter table "public"."match_region_veto_picks" add constraint "match_region_veto_picks_match_id_region_key" unique ("match_id", "region");