Assert current behaviour with clashing index names

dbsrgits · Apr 8, 2020 · b4874ba · b4874ba
1 parent aa48c63
commit b4874ba
Showing 1 changed file with 46 additions and 0 deletions.
diff --git a/t/38-mysql-producer.t b/t/38-mysql-producer.t
@@ -194,6 +194,41 @@ schema:
           type: FOREIGN_KEY
           fields: foo2
           name: fk_thing
+
+    thing4:
+      name: thing4
+      extra:
+      order: 4
+      fields:
+        id:
+          name: id
+          data_type: int
+          is_primary_key: 0
+          order: 1
+          is_foreign_key: 1
+        foo:
+          name: foo
+          data_type: int
+          order: 2
+          is_not_null: 1
+        foo2:
+          name: foo2
+          data_type: int
+          order: 3
+          is_not_null: 1
+      constraints:
+        - type: UNIQUE
+          fields:
+            - foo
+            - foo2
+          name: foo
+        - type: PRIMARY_KEY
+          fields:
+            - id
+        - reference_table: thing
+          type: FOREIGN_KEY
+          fields: foo
+          name: foo
 EOSCHEMA
 
 my @stmts = (
@@ -240,6 +275,17 @@ my @stmts = (
   CONSTRAINT `fk_thing_3` FOREIGN KEY (`foo2`) REFERENCES `some`.`thing2` (`id`, `foo`)
 ) ENGINE=InnoDB",
 
+"DROP TABLE IF EXISTS `thing4`",
+"CREATE TABLE `thing4` (
+  `id` integer NOT NULL,
+  `foo` integer NULL,
+  `foo2` integer NULL,
+  INDEX (`foo`),
+  UNIQUE `foo` (`foo`, `foo2`),
+  PRIMARY KEY (`id`),
+  CONSTRAINT `foo` FOREIGN KEY (`foo`) REFERENCES `thing` (`id`)
+) ENGINE=InnoDB",
+
 "SET foreign_key_checks=1",
 
 );