[Bug]: Connect OceanBase with prisma failed: Unknown system variable 'socket'

[dengfuping]

Describe the bug

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

Environment

• OceanBase Version: 3.2.4.0
• prisma: 5.12.1
• @prisma/client: 5.12.1

Fast Reproduce Steps(Required)

Steps to reproduce the behavior:

• 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

• ✅ Connect with prisma should be success.

Actual Behavior

• ❌ Connect with prisma failed: Unknown system variable 'socket'.

Additional context

• I have been tested OBCloud, self-hosted OceanBase and multiple OceanBase version, and got the same error still.
• TiDB and TDSQL work fine with prisma.
• Related prisma issue:
  • Error: FUNCTION GET_LOCK does not exist prisma/prisma#18508
  • The startup query SELECT @@socket should be ignored when connecting to a remote database prisma/prisma#6207

[hnwyllmm]

Thanks for your report.

[dengfuping]

Thanks for your report.

• What is the root cause and how to fix it?

[hnwyllmm]

This is a mysql compatibility issue and it will be fixed in observer.