Uni Ecto Plugin [2021] <360p>

def index(conn, _params) do # The current tenant was set by the Plug (assigns[:current_tenant]) # But the Repo automatically knows the prefix because Uni.Ecto.put_prefix # is set in the process dictionary. products = Products.list_products() # This calls Repo.all(Product) render(conn, "index.html", products: products) end end

If you are an Elixir or Phoenix developer, you have likely reached for Ecto (the database wrapper and query generator) to handle your data layer. But as your application scales to support multiple organizations or users, you face a classic dilemma: uni ecto plugin

: Built on top of the standard Ecto framework, it leverages existing Changesets and Schemas to provide more efficient data validation and querying workflows. def index(conn, _params) do # The current tenant

: Includes four noise types to control complexity, size, and detail. : Includes four noise types to control complexity,

The true power of uni_ecto is creating new tenants at runtime.

The plugin perfectly maps Ecto’s prefix option. When you write MyApp.Repo.all(User, prefix: "tenant_foo") , uni_ecto translates that to the PostgreSQL schema tenant_foo . This means your standard Ecto queries don't change; only the tenant resolution logic does.