You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a repository where we have four sqlc-generated packages. Currently, sqlc generates the models.go file for each package; which leads to a lot of duplicated code. I was wondering if it would make sense to have an sqlc.yaml config option to create a single models package, which is then used by the query packages.
This issue is related to #835, but I think my feature request goes a bit further as it needs multiple query packages to all refer to the same models package.
What database engines need to be changed?
No response
What programming language backends need to be changed?
Go
The text was updated successfully, but these errors were encountered:
What do you want to change?
I'm working on a repository where we have four sqlc-generated packages. Currently, sqlc generates the models.go file for each package; which leads to a lot of duplicated code. I was wondering if it would make sense to have an sqlc.yaml config option to create a single models package, which is then used by the query packages.
This issue is related to #835, but I think my feature request goes a bit further as it needs multiple query packages to all refer to the same models package.
What database engines need to be changed?
No response
What programming language backends need to be changed?
Go
The text was updated successfully, but these errors were encountered: