db pull with multiSchema error on schema with 2 models with the same table name but in a different schema

[Jolg42]

Bug description

I get the following error when introspecting my PostgreSQL database

Error: [libs/dml/src/datamodel.rs:178:14] Every RelationInfo should have a complementary RelationInfo on the opposite relation field.

How to reproduce

• create schema.prisma file
• create PostgreSQL database from provided SQL
• npx prisma db pull
• Get error

Expected behavior

It should work?

Prisma information

datasource db {
  provider = "postgres"
  url      = env("TEST_POSTGRES_URI")
  schemas  = ["base", "transactional"]
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["multiSchema"]
}

-- CreateSchema
CREATE SCHEMA IF NOT EXISTS "base";

-- CreateSchema
CREATE SCHEMA IF NOT EXISTS "transactional";

--
-- tables names are renamed so they are identical
-- Original names are User and Post
--  

-- CreateTable
CREATE TABLE "base"."some_table" (
    "id" TEXT NOT NULL,
    "email" TEXT NOT NULL,

    CONSTRAINT "User_pkey2" PRIMARY KEY ("id")
);

-- CreateTable
CREATE TABLE "transactional"."some_table" (
    "id" TEXT NOT NULL,
    "title" TEXT NOT NULL,
    "authorId" TEXT NOT NULL,

    CONSTRAINT "Post_pkey2" PRIMARY KEY ("id")
);

-- AddForeignKey
ALTER TABLE "transactional"."some_table" ADD CONSTRAINT "Post_authorId_fkey2" FOREIGN KEY ("authorId") REFERENCES "base"."some_table"("id") ON DELETE RESTRICT ON UPDATE CASCADE;

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v16

Prisma Version

Dev setup with engines 4.5.0-35.7ed9e65490b6d360d03e2b531da2db29b6c7b919

[tomhoule]

The crash is reproduced in a test in prisma/prisma-engines#3297