matthewmueller / matthewmueller/migrate
Support *pgxpool.Pool and *pgx.Conn
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Primarily for programmatic use cases so you don't need multiple connects to the DB to run migrations.
Tricky part will be how to handle transactions within
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
No file or test is named. Start by locating the existing programmatic migration entry point and PostgreSQL connection handling, then trace how connections and transactions are used. Done means migrations accept both *pgxpool.Pool and *pgx.Conn without multiple database connections, with transaction behavior defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100