Uni Ecto Plugin [patched] · Real & Limited

Once your plugin is defined, integration requires just a few lines of code inside your application's Ecto schemas.

# In your Elixir Phoenix Controller def show(conn, %"id" => id) do # Ecto fetch (async-friendly by default in Elixir) user = Repo.get!(User, id) render(conn, "show.json", user: user) end

Here, the first argument ( :org_id ) tells Ecto which field (or fields) to associate the error with. You can use any existing field for this purpose since the actual enforcement comes from the index name specified.

(Ecto.NoResultsError) expected query to return a prefix, but none was set Fix: Ensure your TenantResolver plug runs before any database calls in your controller pipeline. uni ecto plugin

Ecto returns :error, changeset . But what about validation errors vs. database constraint errors vs. connection errors? Uni normalizes all Ecto errors into a standard Uni.Error.t() structure.

The combination of and Ecto offers the best of both worlds:

The Repository acts as the wrapper for the storage engine. It handles the actual lifecycle operations like reading, writing, updating, and deleting data via the validated changesets and queries. Step-by-Step Implementation Guide Installation Once your plugin is defined, integration requires just

+-------------------------------------------------------------+ | Uni-App UI | +-------------------------------------------------------------+ | v +-------------------------------------------------------------+ | Uni Ecto Plugin | | [Schemas] ---> [Changesets] ---> [Queries] ---> [Repo] | +-------------------------------------------------------------+ | v +-------------------------------------------------------------+ | Cross-Platform Storage | | (SQLite / IndexedDB / WebSQL / WeChat Local Storage) | +-------------------------------------------------------------+ Core Pillars of Uni Ecto

In modern game development, choosing the right backend architecture is critical. Developers building massive multiplayer online games (MMOs) or fast-paced real-time games frequently turn to Elixir and the Erlang Virtual Machine (BEAM) for their unmatched concurrency, fault tolerance, and low-latency performance. On the client side, Unity remains the industry standard for creating immersive 2D and 3D experiences.

With the plugin active, developers write standard Ecto queries, and the plugin transparently ensures that deleted data is never accidentally exposed to the end-user. Use Case 2: Multi-Tenant Isolation database constraint errors vs

Have you used the uni_ecto_plugin in production? Share your experiences in the comments below.

defmodule UniEctoPlugin do @moduledoc """ The entry point for the UniEctoPlugin. """ defmacro __using__(mix_mode) when mix_mode in [:schema, :repo] do apply(__MODULE__, mix_mode, []) end def schema do quote do field :row_version, :integer, default: 1 def increment_version(changeset) do Ecto.Changeset.change(changeset, row_version: (changeset.data.row_version || 0) + 1) end end end def repo do quote do # Repository overrides can go here end end end Use code with caution. Step 2: Consuming the Plugin in Your Application

Because plugins alter query behavior implicitly, make sure your team knows they are running. A query that magically appends WHERE deleted_at IS NULL can confuse a junior developer trying to debug a raw SQL issue.

public Uni<UserDTO> fetchUser(String id) // This returns a Uni immediately, keeping the thread free return client.getUser(id) .onFailure().recoverWithItem(fallbackUser);

:telemetry.attach( "uni-ecto-queries", [:uni, :step, :stop], fn event, measurements, metadata, _config -> if metadata.step_module == Uni.Ecto do IO.puts("Step #metadata.step_name took #measurements.durationns") end end, nil )