Consider using tokio-postgres in place of sqlx
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reading the current bdk-sqlx crate and identifying how it uses sqlx. Compare the proposed tokio-postgres replacement and determine the scope of renaming the crate to something like bdk_postgres. Done means the replacement and naming decision are clearly scoped and consistently reflected throughout the project.
Written by the indexing model from the issue text.
Description
And possibly renaming the crate along the lines of "bdk_postgres".
- Dominant language
- Rust
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
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.
More from bitcoindevkit/bdk-sqlx
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bitcoindevkit/bdk-sqlx#20 · 2 comments ·
-
Publish to crates.io Opendiscussion
bitcoindevkit/bdk-sqlx#14 · 5 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
bitcoindevkit/bdk-sqlx#8 · 1 reaction ·
All issues in bitcoindevkit/bdk-sqlx
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·