> I certainly don't think any of this requires insane class inheritance, and maybe that's all people are talking about with OOP. But I still think methods go a long way in this scenario.

Methods at all make a language OOP. Class inheritance is almost a side quest in OOP. (There are OOP languages with no class inheritance.)

Go seems quite object-oriented to me. I would definitely assume it is easier to use an ORM in Go than to not use an ORM.

I don't use a lot of Go, so I can't speak to anything about what the "proper Go" way of doing things is.

I could try to describe some of the non-ORM, functional programming ways of working with databases as I've seen in languages like F#, Haskell, or Lisp, but I'm not sure how helpful that would be to show that CRUD is not "super hard" in FP especially because you won't be familiar with those languages.

The thing I'm mostly picking up from your post here is that you like OOP and are comfortable with it, and that's great. Use what you like and use what you are comfortable with. OOP is great in that a lot of people also like it and feel comfortable with it.

I get how to do CRUD in FP - I don't get how to generate endpoints automatically in FP. Is anybody doing that?