Introspection composite foreign keys pointing to composite primary keys

[matthewmueller]

create table a (
  one integer not null,
  two integer not null,
  primary key ("one", "two")
);
create table b (
  one integer not null,
  two integer not null,
  foreign key ("one", "two") references a ("one", "two")
);
insert into a ("one", "two") values (1, 2);
insert into b ("one", "two") values (1, 2);

model a {
  one Int
  two Int
  bs  b[] @relation(references: [a])

  @@id([one, two])
}

model b {
  a a @map(["one", "two"])
}

The @relation(references: [a]) seems wrong, at least I can't understand this.

[janpio]

Can you run this test again @matthewmueller? The Introspection result should probably be different now.

[matthewmueller]

Is this now the expected result from introspection?

generator client {
  provider = "prisma-client-js"
  output   = "${tmp}"
}

datasource pg {
  provider = "postgresql"
  url      = "${connectionString}"
}

model a {
  one Int
  two Int

  @@id([one, two])
}

/// The underlying table does not contain a unique identifier and can therefore currently not be handled.
// model b {
  // a a @map(["one", "two"])
// }

It gives an unexpected token when parsing, but hopefully that's fixed by the recent merge.

[janpio]

You'll probably get more insight by adding an explicit ID or Unique to the b table. Right now that table is a bit too minimal for PRisma ;)

[do4gr]

Yep, as long as you do not add an ID on b that is the expected result.

[janpio]

Can you please update the integration test to include an explicit ID here @matthewmueller?