prefer_socket doesn't work when connect OceanBase with prisma

[dengfuping]

Bug description

• OceanBase is a MySQL compatible database and doesn't support @@socket variable. [Bug]: Connect OceanBase with prisma failed: Unknown system variable 'socket' oceanbase/oceanbase#1936
• When connect OceanBase with prisma, prefer_socket is configured and doesn't work with following error:

Error: Schema engine error:
Unknown system variable 'socket'

Related prisma issue:

• Error: FUNCTION GET_LOCK does not exist #18508
• The startup query SELECT @@socket should be ignored when connecting to a remote database #6207

How to reproduce

• Clone reproducible repo: https://github.com/dengfuping/prisma-oceanbase-test
• isntall node and npm: https://nodejs.org/en
• run script npm install
• Configure oceanbase connect string in .env.local file
• run script npx prisma migrate dev --name init

Expected behavior

prefer_socket works and connect OceanBase with prisma should be success.

Prisma information

generator client {
  provider = "prisma-client-js"
}

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

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
}

// Add your code using Prisma Client

Environment & setup

• OS: macOS
• Database: MySQL
• Node.js version: v21.6.2

Prisma Version

5.12.1

[SevInf]

Hi @dengfuping
Could you fill an issue template and specify how to reproduce the issue in terms of prisma behavior? I am not sure what the screenshots of our code supposed to signify and I can very much assure you that we have not reverted one of our key components to it's 2021 state in latest Prisma version. Lockfile does not have a link to a commit in quaint repository because there is no separate quaint repository anymore - it is now part of prisma/prisma-engines.

[dengfuping]

Hi @dengfuping Could you fill an issue template and specify how to reproduce the issue in terms of prisma behavior? I am not sure what the screenshots of our code supposed to signify and I can very much assure you that we have not reverted one of our key components to it's 2021 state in latest Prisma version. Lockfile does not have a link to a commit in quaint repository because there is no separate quaint repository anymore - it is now part of prisma/prisma-engines.

• Sorry, I just added more information about the error and reproducible steps.
• As expected, the issue should be fixed in The startup query SELECT @@socket should be ignored when connecting to a remote database #6207, but it occurs again.

[dengfuping]

@SevInf A OceanBase connection string is available for testing.

[dengfuping]

@SevInf I have sent an OceanBase connection string to your email with my mail dengfuping_private@163.com so that you can test it. Thanks a lot.

[janpio]

With the provided oceanbase connection string, I can confirm that the Prisma schema engine indeed fails with Error: Unknown system variable 'socket'. I can also confirm that in a real MySQL, everything works. I think this is not a bug in Prisma, but a problem of Oceanbase that is out of our control.

@dengfuping What exactly do you refer to with prefer_socket? Where is that used or configured? Adding it to the connection string with ?prefer_socket=true or ?prefer_socket=false does not change anything.

[janpio]

Oceanbase has acknowledged this and is working on a fix: oceanbase/oceanbase#1936 (comment)