db push --force-reset is not creating database if it doesn't exist

Bug description

running npx prisma db push --force-reset for a database that does not exist gives me an error instead of creating the database.

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "mydb-test", schema "public" at "localhost:5432"

Response: Database `mydb-test.public` does not exist on the database server at `localhost:5432`.
Error: UserFacingError

If I manually create the database using the same user then running npx prisma db push --force-reset my schema is correctly setup.

With debug output

DEBUG="*" npx prisma db push --force-reset                                                                                                         ─╯
  prisma:loadEnv project root found at {MY_PATH}/backend/package.json +0ms
  prisma:tryLoadEnv Environment variables loaded from {MY_PATH}/backend/.env +0ms
Environment variables loaded from .env
  prisma:engines using NAPI: false +0ms
  prisma:engines binaries to download query-engine, migration-engine, introspection-engine, prisma-fmt +1ms
Prisma schema loaded from prisma/schema.prisma
  prisma:getConfig Using Query Engine Binary at: {MY_PATH}/backend/node_modules/@prisma/engines/query-engine-darwin +0ms
Datasource "db": PostgreSQL database "mydb-test", schema "public" at "localhost:5432"
  prisma:getConfig Using Query Engine Binary at: {MY_PATH}/backend/node_modules/@prisma/engines/query-engine-darwin +51ms

  prisma:migrateEngine:rpc starting migration engine with binary: {MY_PATH}/backend/node_modules/@prisma/engines/migration-engine-darwin +0ms
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":1,"jsonrpc":"2.0","method":"reset","params":{}} +18ms
  prisma:migrateEngine:stderr Jun 03 15:42:09.053  INFO migration_engine: Starting migration engine RPC server git_hash="f3e341280d96d0abc068f97e959ddf01f321a858" +0ms
Error: Error: UserFacingError
    at ChildProcess.<anonymous> ({MY_PATH}/backend/node_modules/prisma/build/index.js:57396:28)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:467:12)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)

This was working fine until I tried to run my integration tests today.

I was on 2.23.0 when I first saw the error and then tried on 2.24.0 and saw the same issue.

How to reproduce

run npx prisma db push --force-reset

Expected behavior

A database is created if it does not already exist

Prisma information

now it's closed I've removed the schema that was pasted here

Environment & setup

• OS: MacOS BigSur 11.4
• Database: PostgreSQL 13.2 (Debian 13.2-1.pgdg100+1)
• Node.js version: 14.16.1

PostgreSQL is running in a docker container with an exposed port of 5432 prisma is running on host os

Prisma Version

prisma               : 2.24.0
@prisma/client       : 2.24.0
Current platform     : darwin
Query Engine         : query-engine f3e341280d96d0abc068f97e959ddf01f321a858 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli f3e341280d96d0abc068f97e959ddf01f321a858 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core f3e341280d96d0abc068f97e959ddf01f321a858 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt f3e341280d96d0abc068f97e959ddf01f321a858 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : f3e341280d96d0abc068f97e959ddf01f321a858
Studio               : 0.397.0

[tomhoule]

Starting migration engine RPC server

This should not be showing up in the error, we need to look into that as well. It’s probably a problem with the new error handling code in the CLI.

[pantharshit00]

I can reproduce this with 2.25. Looks like only happening with --force-reset