three VS golang-database-library-orm-example

I've been using https://github.com/soypat/three for 3D rendering. Not really Go behind the scenes, but at least you get to write what looks like Go.

Generating interface implementation for javascript bindings using gopherjs https://github.com/soypat/three

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