Anyone here storing the sqlc-generated code in an internal sub-package?

[preslavrachev]

We've been toying around with the idea of moving future sqlc exports into an internal sub-package (e.g. db/internal). The idea is to put a more domain-specific facade between the rest of the code and the DB layer. Not that the sqlc code is bad by itself, but it will always remain primarily DB focused - everything there, from the types of optional params, to the types of errors lives and breathes SQL - we'd rather like the rest of the code to think of a bit higher abstraction.

I was wondering if anyone else has done it. Was it worth it in the end? It's quite a bit of boilerplate "facade" code to begin with.