Set the default schema name from configs. #2966
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The codebase already has the "Default schema" term. But unfortunately, it is hardcoded in the codebase as "public" for the PostgreSQL. It cannot be changed from configs. And this is the problem in such a situation:
I have several services with separate schemas in a database. For example, the "auth microservice" has its own schema "auth" in the DB. All parts of this microservice work only with this schema and no one else. In terms of codebase, I have entities like AccessToken, Account, etc. But SQLc generates me structs like AuthAccessToken, AuthAccount, etc. This Auth prefix is redundant and I don't have the ability to switch off it.
This request solved this issue it added the changing of the default schema, which asked SQLc to generate Entities without the schema name as a prefix.