Question

Hello maintainers,

I’m interested in working on support for KingbaseES in Prisma over the next couple of months, and I wanted to ask first whether this kind of contribution would be acceptable to the community and maintainers.

Based on my initial research, KingbaseES has a certain level of compatibility with parts of the PostgreSQL/MySQL ecosystem, which makes me think this adaptation may be technically possible.

To keep the contribution safe and maintainable, my goal would be to:

• keep the design as non-intrusive as possible
• avoid breaking or affecting existing supported databases
• add targeted integration tests for compatibility-related behavior
• follow Prisma’s contribution guidelines and update documentation if needed

I have already started some preliminary validation, and if this direction is considered acceptable, I’d be happy to continue and work toward a Pull Request in the coming months.

Would Prisma maintainers be open to this kind of database adaptation for KingbaseES? If there are any architectural expectations or constraints I should be aware of before starting, I’d really appreciate your guidance.

Thank you.

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// Add your schema.prisma

// Add any relevant Prisma Client queries here

• OS:

• Database:

• Node.js version:

• Run prisma -v to see your Prisma version and paste it