Skip to content

Export models to a different package #835

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
td0m opened this issue Dec 17, 2020 · 4 comments · May be fixed by #3874
Open

Export models to a different package #835

td0m opened this issue Dec 17, 2020 · 4 comments · May be fixed by #3874
Labels
enhancement New feature or request

Comments

@td0m
Copy link

td0m commented Dec 17, 2020

Hi! Great work on this project!

I was wondering if it's currently possible to export Go model structs to a different folder package.

I think this could be a good feature for anyone who would like to make their code independent of the database backend but still use the automatically generated models.

For example:

internal/
  model/
    models.go
  db/
    postgres/
      db.go
      user.sql.go
      querier.go

This way you could e.g. also have a mongodb provider that uses these models, but without depending on the postgres package. I'm sure you'd agree that it would be odd for mongo to use postgres.User as a type.

Is this something that's possible to do? If not, would you possibly accept a PR that adds support for it? Or it it something you're not planning on supporting for now?

Thanks
@kyleconroy kyleconroy added the enhancement New feature or request label Jan 25, 2021
@GeertJohan GeertJohan mentioned this issue Nov 9, 2022
Open
@taylow taylow mentioned this issue Nov 10, 2022
Open
@johan-lejdung
Copy link

We just tried this out at our company, for context we are using go-migrate so we have a single folder with all of our database migrations. Without a feature like this the, otherwise excellent sqlc, isn't a viable option for us.

As it stands (unless I've missed some configuration?) each generated package has a models.go file containing all models from our entire database.

Having an option to decide where to generate the models file, and read from it on the subsequent generated packages OR being able to remove unused models would be a much needed feature.

I see this has been left untouched since 2020, is there anything I can do to help speed this along?

@mpyw
Copy link
Contributor

mpyw commented Jul 6, 2023

#1941 (comment)

This was referenced Sep 26, 2023
Closed
Closed
@kyleconroy kyleconroy mentioned this issue Oct 19, 2023
Closed
@anhnmt
Copy link

anhnmt commented Jan 3, 2024

+1

@MWT-proger MWT-proger mentioned this issue May 13, 2024
Closed
5 tasks
@kyleconroy kyleconroy moved this to 🔍 Exploring in sqlc Roadmap Jun 5, 2024
@mmierzwa
Copy link

Still waiting for this at the end of 2024 😊

@berk-karaal berk-karaal linked a pull request Mar 6, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
sqlc Roadmap
Status: 🔍 Exploring
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(codegen/golang): Allow exporting models to a different package berk-karaal/sqlc
6 participants
@kyleconroy @mpyw @mmierzwa @johan-lejdung @td0m @anhnmt