Introspection tells me ⠋ Introspecting MySQL schema with 1 tables. during introspection

[janpio]

... but MySQL doesn't have schemas:

⠋ Introspecting MySQL schema  with 1  tables.

The spacing in the output also seems wonky in general.

(This appears only shortly while the introspection is running, after a connection was successfully made.)

[janpio]

For Postgres it says:

⠋ Introspecting PostgreSQL database foo with 1  tables.

🌀

[pantharshit00]

Can you please tell me the exact steps for this? I wasn't able to reproduce when I tried it.

[janpio]

Internal link https://github.com/prisma/prisma-cli-blackbox-tests/runs/267432579 can tell you the exact steps for Postgres for example: Click Run node init-flow-test.js prisma2 blank_postgres_with_exists_notempty_ts_schema and then scroll down to line 5221 to see it - go back up to see the steps (Blank, Postgres, Enter credentials with DB and Schema of a not empty schema, observe).

[janpio]

Note to myself:
Strings for MySQL and Postgres seem to be switched here:

• MySQL says schema and can't show one, because MySQL does not have that
• Postgres says database and shows something, probably the schema

Also additional space after the number in both cases.

[pantharshit00]

Internal link prisma/prisma-cli-blackbox-tests/runs/267432579 can tell you the exact steps for Postgres for example: Click Run node init-flow-test.js prisma2 blank_postgres_with_exists_notempty_ts_schema and then scroll down to line 5221 to see it - go back up to see the steps (Blank, Postgres, Enter credentials with DB and Schema of a not empty schema, observe).

The link is broken now :/

[janpio]

Added you as collaborator.

[pantharshit00]

Ok, I can also reproduce this now:

[divyenduz]

@janpio @pantharshit00 does this still apply with the new introspection? If no, please close it. Thanks.

[pantharshit00]

Yes, this is still relevant:

It is probably a printing issue in the CLI.

[janpio]

To recap:

• Database and schema are mixed up between MySQL and Postgres
• There was additional spacing after the number of tables sometimes

[Jolg42]

This is not applicable anymore, the screenshots show the old interactive CLI that was removed.
We do have this https://github.com/prisma/migrate/blob/master/src/utils/ensureDatabaseExists.tsx
It will create a database (the term should be the same for all db here as it's a different scenario, ie: not creating schema/tables) if non existing when doing migrate save down or up.