Consider using tokio-postgres in place of sqlx

Open
#2 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend, databases

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

discussion

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bitcoindevkit/bdk-sqlx

All issues in bitcoindevkit/bdk-sqlx

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.