rivermigrate using a single connection instead of a pool
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 179
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 13
Description
Hello!
River is an excellent piece of software, I'm in love with it :)
Recently, I tried to integrate river migration with the migration tooling that uses pgx/v5's pgx.Conn to drive the migration instead of a pgxpool.Pool. Unfortunately, River does not seem to support it. Previously it supported pgx.Tx, but then it was removed.
Are you open to add support for pgx.Conn/generic single connection?
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 tracing rivermigrate's existing integration with pgx/v5's pgxpool.Pool and compare the required operations with pgx.Conn. Confirm which migration entry points currently require a pool and define completion as supporting a single connection without regressing pool-based migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100