I like that you offer an alternative, I loved chaining in JS but I don't think they belong to a Go code.
Offtopic: I am surprised that ORM's are still used nowdays. So many restrictions, is like a framework over a framework that tells you how to do it. I hit so many problems over the years that I don't get it how is still alive. The only benefit it offers will most probably fail and I never saw a team use it (switch to other SQL database).
Especially now when you have so many data storage types accessible and services (loggers, graph databases, noSQL documents, event sourcing).
Especially in a language where you do not have Objects! from ORM
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like that you offer an alternative, I loved chaining in JS but I don't think they belong to a Go code.
Offtopic: I am surprised that ORM's are still used nowdays. So many restrictions, is like a framework over a framework that tells you how to do it. I hit so many problems over the years that I don't get it how is still alive. The only benefit it offers will most probably fail and I never saw a team use it (switch to other SQL database).
Especially now when you have so many data storage types accessible and services (loggers, graph databases, noSQL documents, event sourcing).
Especially in a language where you do not have Objects! from ORM