golang-database-library-orm-example VS GORM

What I found is sqlx and sqlc are excellent for hand-rolled queries, but is poor for dynamic queries which a query builder library/orm might suite better. If there are many eager-loading table relationships, I found that orms tend to be much better. Of course these are entirely my personal opinion. I dove into more details on how each libraries and orms fares against those operations in the posts. It is also accompanied with reproducible repo at https://github.com/gmhafiz/golang-database-library-orm-example

I discussed approaches using different libraries and ORMs at https://www.gmhafiz.com/blog/golang-database-library-orm-example-dynamic-list/. Though I just realised the example for squirrel is missing. Check out the code examples though

I show scans for a many to many relationship between two tables. https://github.com/gmhafiz/golang-database-library-orm-example/blob/master/db/sqlc/manyToMany.go

I made repo that compares between different libraries and orms including sqlx, sqlc, sqlboiler, gorm, and ent https://github.com/gmhafiz/golang-database-library-orm-example

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