Closed kysshsy closed 2 months ago
Because pg_analytics
has a dependency that also uses pgrx (the supabase-wrappers
), instead of modifying Cargo.toml
the way you did, add this at the end:
[patch.crates-io]
pgrx = { path = "/home/kyss/labs/pgrx/pgrx"}
That should clue cargo into using your version of pgrx for the top-level pg_analytics crate and all its dependencies that need it.
Hi @eeeebbbbrrrr, I have a similar situation, but my Cargo.toml
does not include PGRX. We do have a dependency that includes it, but this project itself doesn't. Is there a way to overcome this issue?
Adding the PGRX as dependency would be a solution, but in this case I would have to add that pgrx_embed!
macro too. And I would like to avoid that.
pgrx isn't meant to be a transient dependency. You'll need to structure your code with that in mind.
I want to build with local repo of pgrx and expose some functions of Postgres. So I changed the Cargo.toml.
pgrx = {path = "/home/kyss/labs/pgrx/pgrx"}
and I rungit checkout v0.12.4
in pgrx repo.And run
cargo build
in pg_analytics repo(which use pgrx as a dependency).Cargo.toml