When running this repo, I get the following error:

error[E0277]: the trait bound `Postgres: sqlx_core::database::Database` is not satisfied
  --> src/main.rs:51:13
   |
51 |     mut tx: Tx<Postgres>,
   |             ^^^^^^^^^^^^ the trait `sqlx_core::database::Database` is not implemented for `Postgres`
   |
   = help: the trait `sqlx_core::database::Database` is implemented for `sqlx_core::postgres::database::Postgres`
note: required by a bound in `Tx`
  --> /home/nyx/.cargo/registry/src/github.com-1ecc6299db9ec823/axum-sqlx-tx-0.3.0/src/tx.rs:75:19
   |
75 | pub struct Tx<DB: sqlx::Database, E = Error>(Lease<sqlx::Transaction<'static, DB>>, PhantomData<E>);
   |                   ^^^^^^^^^^^^^^ required by this bound in `Tx`

Is this a bug or something I can solve myself? If the latter, how may I do that?

• 3d915de feat: add Error generic type to Tx

  This allows callers to choose the error type of the FromRequest implementation, as long as it implements From<Error> + IntoResponse.

• ea12b73 refactor: move Error from tx to root

  This is in preparation for using Error in Layer.

• 935c27e refactor!: make Service infallible

  Service's associated Error type is now Infallible, meaning it can be used with axum::Router::layer directly, without any HandleErrorLayer shenanigans.

  This was achieved by using Error to convert any sqlx::Errors on commit into a response. The downside of this is that the error message will be returned to clients, but this will be fixed subsequently.

  BREAKING CHANGE: It's no longer possible to layer axum_sqlx_tx::Layer with HandleErrorLayer, it should be layered on its own instead.

• 8ace093 refactor: add Error generic type to Layer

  This allows callers to choose the error type that's converted to a response in the event that committing returns an error.

  To maintain backwards compatibility, and ergonomic default usage, a separate Layer::new_with_error function is needed to create a Layer with an error type other than Error.

• f9f7b1e doc: flesh out error handling documentation

  This includes examples of using the E generic type parameter to control how errors are converted to responses.

• 0ba85c9 chore: bump version

• e241e9e doc: flesh out the documentation

  All types are now well covered for prose, and there are a few more examples in the docs. Additionally, a full example has been added.

• 7f9bd79 chore: bump version

• ce810c1 ci: add cargo doc check to CI

• be0673a ci: add a simple release workflow

  Currently this just invokes cargo publish when a semver tag is pushed to the repo. Ideally there should be some extra verification and/or automation around the version number, but this gets it off my laptop for now.

• 8afc9e9 refactor: use an Arc<Mutex<Option<_>>> for slot

  This should be a bit smaller and more efficient than the oneshot shenanigans since oneshot itself uses an Arc and several locks internally.

• 27f5022 chore: use futures-core rather than futures

  Now that we don't need futures::channel::oneshot we can get away with only futures-core.

• e5f9710 chore: add .sublime-project

  Since we need some features to be enabled for rust-analyzer to run properly, it makes sense to put them in a project-specific configuration.

• 353d6b9 chore: bump version

• Upgraded axum to v0.6
• Implemented FromRequestParts for Tx instead of FromRequestParts so that it won't consume the request body
• Implemented Clone for axum_sqlx_tx::Layer as it is needed by axum layer
• Since Error type can't be cloned, removed it from the axum_sqlx_tx::Layer.
  • For custom error response for axum_sqlx_tx::Layer use axum::error_handling::HandleErrorLayer
  • For customizing error response for extractor rejections use custom extractors. See the customize-extractor-error example for more details

The 303 See Other response is often used to direct clients to another page after successfully creating a new resource, and such behavior is encouraged by web standards.

Thanks for this module, it's very useful. I'm using it to develop a web application.