Any plan to use some ORM package in the backend?

[suzaku]

It seems like there are many boilerplate code here and there just for making similar queries.

[tianzhou]

I personally prefer to use plain sql since it's not that complex and it gives us the best control. I did think of considering sqlc if I would start the project from scratch (we may still adopt this in the future as we have some early idea to do code generation based on SQL).

BTW, which ORM would you recommend?

[suzaku]

Good to know that it's by design. I agree with you that we have to give in some flexibility if an ORM is used. That said, if boilerplate code keep growing, we'll need to come up with some solution to eliminate duplication.

I haven't used an ORM that I really like in all cases, but when I tried ent it kind of surprised me by how far we can go with go generate.

Maybe it's better to wait for Go 1.18 and see if the implementation can be simplified with generics.

[tianzhou]

Haven't tried ent before. Good to know.

Yeah, let's wait for a while~