Error parsing attribute "@relation" when unique/id index is in different order

Bug description

The Prisma model will not generate if there is a valid key whose columns are in a different order than it expects them.

How to reproduce

1. Create a model from the template below
2. See the file and observe the highlighted error

Expected behavior

It should work.

Prisma information

model nabzak {
  offerID         Int             @db.UnsignedSmallInt
  periodID        Int             @db.UnsignedSmallInt
  carrierID       Int
  reservation     String?         @db.Char(2)
  wanted          Int?            @db.TinyInt
  carrierInPeriod CarrierInPeriod @relation(fields: [offerID, periodID, carrierID], references: [offerID, periodID, carrierID], onDelete: Cascade, onUpdate: NoAction)

  @@id([offerID, carrierID, periodID])
  //@@unique([offerID, periodID, carrierID]) // This would fix it, but it is not necessary as for uniquess the order of columns does not matter
  @@index([offerID], map: "idZak")
  @@index([offerID, periodID, carrierID], map: "nabzak_zaknos")
  @@index([carrierID], map: "ncis")
}

model CarrierInPeriod {
  offerID   Int     @map("idZak") @db.UnsignedSmallInt
  periodID  Int     @map("idObdobi") @db.UnsignedSmallInt
  carrierID Int     @map("ncis")
  nabzak    nabzak?

  @@id([offerID, periodID, carrierID])
  @@index([offerID, periodID], map: "IDZak & IDObdobi")
  @@index([offerID, carrierID], map: "IDZak & ncis")
}

Environment & setup

• OS: Windows
• Database: MySQL
• Node.js version: v16.13.2

Prisma Version

prisma                  : 4.1.1
@prisma/client          : 4.1.1
Current platform        : windows
Query Engine (Node-API) : libquery-engine 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Migration Engine        : migration-engine-cli 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine    : introspection-core 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary           : prisma-fmt 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash    : 8d8414deb360336e4698a65aa45a1fbaf1ce13d8
Studio                  : 0.469.0
Preview Features        : interactiveTransactions

[Akxe]

@janpio @tomhoule I have used the expression SET foreign_key_checks = 0 to disable foreign key checks off.

[Akxe]

So the bug should be that uniqueness of fields are guaranteed by @@unique and @@id in any order of the combined fields, not just by the one in use in fields. Correct @Akxe?

@janpio Yes but, I am not sure if it is MySQL only error