prisma.$connect() not invoking error on turned off database

[ElectricReality]

Bug description

In the case of a failed connection, prisma should be calling the error PrismaClientInitializationError. Using the following code to connect:

import Prisma from '@prisma/client';
const { PrismaClient } = Prisma;
const prisma = new PrismaClient();

async function connecttodb() {
	console.log('Connecting to the database using PRISMA CLIENT.');
	try {
		await prisma.$connect();
		console.log('Connected to the database!');
	} catch (error) {
		console.error('Failed to connect to the database.', error);
	}
}

export { prisma, connecttodb };

the line, await prisma.$connect() should throw an error when the DATABASE_URL environment is unconnectable or unreachable. However, it does not.

Though, it throws an error when a query is called:
ConnectorError(ConnectorError { user_facing_error: None, kind: RawError { code: "unknown", message: "Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: localhost:27017, Type: Unknown, Error: No connection could be made because the target machine actively refused it. (os error 10061) }, ] }" } })

Possible related issue/s: #6431

How to reproduce

1. Turn off the database
2. Run the function connecttodb()
3. Prisma will not return a error.

Expected behavior

It's expected for prisma to throw the error PrismaClientInitializationError. According to the documentation, it should be invoked if something goes wrong when the query engine is started and the connection to the database is created.
This happens either:

• When prisma.$connect() is called OR
• When the first query is executed

If i'm getting anything wrong in regards to the "query engine is started and the connection to the database is created". Feel free to correct me. Though, it's still best that the error should be called on connection initialization to prevent further errors in production.

Prisma information

Connection code:

import Prisma from '@prisma/client';
const { PrismaClient } = Prisma;
const prisma = new PrismaClient();

async function connecttodb() {
	console.log('Connecting to the database using PRISMA CLIENT.');
	try {
		await prisma.$connect();
		console.log('Connected to the database!');
	} catch (error) {
		console.error('Failed to connect to the database.', error);
	}
}

export { prisma, connecttodb };

Prisma schema:

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

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

Environment & setup

• OS: Windows 10 Pro 21H1
• Database: MongoDB
• Node.js version: v16.3.0

Prisma Version

Prisma Client: 2.26.0

[ElectricReality]

Closing since it seems to be resolved in Prisma client version 2.27.0. Thank you!

[vishalxtyagi]

Hello, I've had a same problem with prisma when using'mysql'.

[abdelhalim97]

same here i m runing prisma 5 with mysql and it doesnt show error message when the data base url is wrong
prisma 4 on Postgres is working fine

[janpio]

Please open a new issue and provide all the information the bug templates asks for.

[abdelhalim97]

sorry the problem i was not calling the connecttodb on any provider
its working now