docs.rs failed to build arium-pool-0.1.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
arium-pool
Compile-time-selected sqlx pool aliases — the one place the backend
(sqlite vs postgres) is chosen.
Enable exactly one of the sqlite or postgres features. Both the arium
auth engine and arium-authz depend on this crate, so they agree on a
single concrete Pool type and a single "exactly one backend" guard:
a feature-unification mistake fails here, loudly, rather than as a cryptic
SqlitePool-vs-PgPool mismatch deep in a transaction signature.
Installation
Enable exactly one backend feature — there is no default, so the backend is chosen once at the top of the dependency tree and forwarded down:
[]
= { = "0.1", = ["sqlite"] } # or "postgres"
Full API reference on docs.rs. Key aliases: Pool, DbBackend, DbConnection.
License
Licensed under either of:
at your option.