Migration failed: pq: relation "gorp_migrations" does not exist
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 292
- PR merge metrics
- No merged PRs in 30d
Description
Any reason why this could be happening? I checked my permissions for the user to access the DB and it looks good to me...what else can I be missing? Also it does seem like the sql-migrate up command too is creating the gorp_migrations table too.
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 by reproducing the failure with the PostgreSQL database and the sql-migrate up command. Trace when sql-migrate creates and accesses the gorp_migrations table, then determine why the relation is missing despite the reported permissions. Done means the cause and expected migration behavior are established and documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100