init, Introspection: Tells me that schema is not empty, does not even exist though

[janpio]

When introspecting a Postgres DB for a "Starter Kit" init run, I entered database postgres and schema my_db. Something goes wrong, and the error message tells me that schema 'postgres' is not empty. Something is getting confused here.

C:\Users\Jan\Documents\throwaway>prisma2 init dafasdf3422

 SUCCESS  Connected to PostgreSQL database as postgres

The PostgreSQL schema `postgres` is not empty.
When using a starter kit, you must provide an empty schema.
Create a new PostgreSQL schema or use an empty one.

┌─ Database options ──────────────────────────────────────────────────────┐
│                                                                         │
│ > Create new PostgreSQL schema   Start from scratch                     │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘

< Back (Database credentials)

[pantharshit00]

I am able to reproduce this.

This occurs when you put the schema in the Schema(optional) field in the database credentials form. It is not being used by the cli

[divyenduz]

@pantharshit00 can you please quickly re-triage this one?

[janpio]

This is currently not reproducible as the database/schema entered in the credentials form is completely ignored. Will have to be retested when this is fixed.

[janpio]

We will replace the existing init wizard with a much simpler version in 2.0.0-preview020, so this problem will be gone after that 🚀