prisma-client-go VS prisma-client-rust

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.

I build simple rust axum api server with Prisma client rust. This is my something done with rust and I really enjoyed rust!

Prisma Client Rust. If you come from the JS/TS world this fits right in. It's halfway between a full ORM and SQL(x), so I prefer it.

Wut, Prisma works with Rust?! Is this what you're referring to? : https://github.com/Brendonovich/prisma-client-rust

There's Prisma Client Rust if you want a fully fledged ORM!

Damn, I use Prisma, it's a good way to have a unified database schema for which you can generate code in any language you want. It was very useful for converting a TypeScript project to a Rust one, I use prisma-client-rust in particular.

https://github.com/Brendonovich/prisma-client-rust

I also come from the NodeJS world where I used Prisma as an ORM / query builder. Turns out since the schema is language agnostic, anyone can make clients for it for any language, including Rust. I made a simple example which combines Prisma Client Rust, Actix Web, and Async GraphQL together, fairly straightforward to make.

I've been using prisma client rust instead of seaorm lately and have been very happy