prisma-client-go VS GORM

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.

GORM is a comprehensive ORM tool in Go, offering a code-first approach which allows defining database schemas using struct tags in Go. It's known for its developer-friendly nature, making it suitable for both beginners and experienced users. GORM supports a variety of SQL databases like MySQL, PostgreSQL, and SQLite. It's designed to be flexible, allowing developers to drop down to raw SQL when necessary. However, it's important to be cautious about its performance implications in large-scale applications.

Homepage: https://gorm.io/

Since most of these APIs will be simple CRUD (Create/Read/Update/Delete) endpoints, let's build this service using GORM, an ORM library that makes building CRUD endpoints really simple.

After successfully configuring the application, it's time to delve into integrating the data layer. For this purpose, I will utilize gorm, a powerful SQL ORM that facilitates rapid development of the data layer using model structs.

For basic INSERT ... VALUES ... or SELECT ... WHERE ... JOIN ..., use a library such as GORM. For INSERT .... SELECT ... statements where one combines two round trips (SELECT and INSERT) into one, ORMs have a hard time performing this query. Particularly when you start doing joins. Joins are the heart of Relational database theory (they denote relationships). So get to know what an INNER, LEFT, RIGHT and OUTER join is and why you would use them. Also learn INSERT ... SELECT ...

I have never hated gorm and it serves me well. However I tend to feed it raw SQL very often.

Array of values with embedded value all pointed to the last value, reflect code was broken: https://github.com/go-gorm/gorm/pull/5901 data corruption