schema field in dbconfig.yml being ignored
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 292
- PR merge metrics
- No merged PRs in 30d
Description
As titled, yml file is being used for user, db password etc, but completely ignores the schema argument: it simply targets the default schema, "public"
dbconfig.yml file below:
development:
dialect: postgres
datasource: dbname=postgres sslmode=disable user=postgres password=postgres
schema: click
dir: db/psql/sql
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dbconfig.yml example and trace how its schema value is handled for the postgres dialect. Reproduce the migration using schema: click, then verify that migrations target click rather than the default public schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100