prisma-client-go VS quaint

The same company that stopped officially maintaining their golang library when it wasn't getting "the growth we were hoping for".

https://github.com/prisma/prisma-client-go/issues/707

I mistakenly write 'Python' while I actually meant 'Go', see prisma-go-client here. The idea is the same of course

Prisma Go implementation is no longer maintained...shame: https://github.com/prisma/prisma-client-go

From the schema, a TypeScript Prisma Client can be generated that can be used in Node.js applications - including Next.js! A Go Prisma Client is also in the works.

This is why https://github.com/prisma/prisma-client-go works via code generation and generates a complete query builder and return types for your database schema. It integrates with the Prisma ecosystem, so you can also make use of declarative migrations and more.

That is only used in tests :) The query engine uses this: https://github.com/prisma/quaint/blob/6532d69b5aec007ad06ac6...

(I work at Prisma, could have mentioned that earlier)

Just a quick note about this point: We do use the standard Rust drivers for the DBs we support (e.g. tokio-postgres or the official MongoDB driver for Rust) and don't write/maintain our own drivers, you can see this from our Cargo.toml.

I'm using https://github.com/prisma/quaint/ with mssql. As far as I understand, it wasn't released to crates.io for two year only because of some dependencies issues with postgres (https://github.com/prisma/quaint/issues/264)