Prisma Studio v7 + mysql/mariadb - "introspect" operation failed
Hey,
I just migrate my project to Prisma 7, its work, but studio does not work.
When i try open, it says: "introspect" operation failed - No Tables Found
Is there any bug?
How can I fix it?

17 Replies
You selected the carefully hand-crafted route. A dev artisan will respond soon. Meanwhile, the
#ask-ai channel awaits if you're curious!Same issue
I am checking this.
Any result?
Almost same issue
but with postgres

// prisma.config.ts
import 'dotenv/config'
import { defineConfig, env, PrismaConfig } from 'prisma/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
datasource: {
url: env('DATABASE_URL'),
},
}) satisfies PrismaConfig
I wasn't able to reproduce this for postgres.

I have no idea
I took the default config from prisma postgres connection page
Is your repo open source?
literally copied and paste just to see if it was a mistake on my side
Sadly not and it's under NDA
I can share everything related to prisma though
db.ts
Could you create a GitHub Issue and add information it asks for and the one you can provide: https://github.com/prisma/prisma/issues
I'll get this checked with our ORM team
GitHub
prisma/prisma
Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB - prisma/prisma
Sure
Yep, basic and simple config... impossible run the studio
Hey 👋
MariaDB is not supported yet in this iteration - only PostgreSQL, MySQL and SQLite. You're seeing it trying to do MySQL-specific stuff and fail. Sorry about that. Issue being tracked in https://github.com/prisma/studio/issues/1367.
@FrancyMak this issue is tracked in https://github.com/prisma/studio/issues/1363 and has a solution review pending. Sorry about that.
As a temporary workaround, you can remove the schema query parameter from your connection string before starting Studio.
I'm on prisma postgress
i don't have that string
