Extensions `$connect` method is not used by Prisma query methods unless it's invoked explicitly about prisma HOT 3 OPEN

In my case, I was just testing more effective ways to send connection exceptions to a logging service, which in the end I did by just leveraging the $on error event.
I opened the bug anyway because I noticed some official Prisma extensions do override $connect in some cases (e.g. https://github.com/prisma/extension-read-replicas).

from prisma.

Sorry, forgot to markdown

const prisma = new PrismaClient()

const prismaExtension = prisma.$extends({
  client: {
    async $connect() {
      console.warn('Connecting to database')
      await prisma.$connect()
    }
  }
})

prismaExtension.user.findFirst() // Won't log 'Connecting to database'
// prismaExtension.$connect() // Will log 'Connecting to database'

from prisma.

This is generally true for non-extended $connect too - executing request will establish the connection to the database, but it will not do so by calling the same public $connect method. What is a usecase for overriding $connect? Generally, client extensions are meant for additions on top of public client API, not for altering internal behaviours.

from prisma.