Proposal: official Drizzle adapter support for mysql-next

[luas10c]

Hi Drizzle team,

I’d like to propose an evaluation for official support of mysql-next as a MySQL driver adapter in Drizzle.

At the moment, Drizzle’s MySQL documentation and driver guides point users to mysql2 as the native/default Node.js option for MySQL usage. :contentReference[oaicite:0]{index=0}

I’m the author of mysql-next, and I built it as a more modern MySQL driver for Node.js with a focus on developer experience, modern API design, and performance-oriented usage for current TypeScript/Node environments.

Package:

• mysql-next on npm https://www.npmjs.com/package/mysql-next

What I’m asking for:

• An evaluation of whether mysql-next could be supported officially by Drizzle
• Guidance on the minimum compatibility surface required for a first-party adapter
• Feedback on whether this should start as a community adapter first, then move toward official support

Why I think it may be worth considering:

• Drizzle already has strong driver-specific integrations, and MySQL currently routes users toward mysql2 for official support. :contentReference[oaicite:1]{index=1}
• A dedicated adapter for mysql-next could expand the MySQL ecosystem around Drizzle without changing the ORM experience itself
• I’m willing to help with implementation, compatibility work, testing, and maintenance if this is something the team is open to

I’d be happy to provide:

• a compatibility layer matching the expectations of Drizzle’s MySQL driver integration
• example projects
• test coverage against Drizzle queries/migrations
• benchmarks and behavioral comparisons where useful

If the team is open to it, I’d appreciate feedback on:

1. whether this fits Drizzle’s direction for MySQL driver support
2. what adapter interface/contracts need to be satisfied
3. whether you’d prefer an external package first before considering official support

If useful, I can also open a draft PR or a proof-of-concept adapter implementation.

Thanks