zimt28

zimt28

In my application I want to have a single entities table, which stores type a and type b entities. type a and type b share the exact same fields, I just set a type field can be "type_a" or "type_b".

For some reasons I don’t want to work with %Entity{} structs, but %TypeA{} and %TypeB{} structs, and I’m now wondering what might be the best way to do this.

In the end I’m looking for a way to create “aliases” for my %Entity{} struct. Here’s what I’ve tried so far:

1. Just define the schema multiple times

defmodule App.Entities.Entity do
  # ...

  schema "entities" do
    field :title, :string
    field :type, :string
    has_one :address, Address
  end

  @doc false
  def changeset(%Entity{} = entity, attrs) do
    entity
    |> cast(attrs, [:title, :type])
    |> validate_required([:title, :type])
  end
end

defmodule App.Entities.TypeA/B do
  # ...

  schema "entities" do
    field :title, :string
    field :type, :string
    has_one :address, Address, foreign_key: :entity_id
  end

  @doc false
  def changeset(%TypeA/B{} = entity, attrs) do
    entity
    |> cast(attrs, [:title, :type])
    |> validate_required([:title, :type])
    |> put_change(:type, "type_a/b")
  end
end

This works fine, but I don’t like the repetitiveness of this approach.

2. Use a separate schema module

defmodule App.Entities.EntitySchema do
  defmacro __using__(_) do
    quote do
      # ...

      schema "entities" do
        field :title, :string
        field :type, :string
        has_one :address, Address, foreign_key: :entity_id
      end
    end
  end
end

defmodule App.Entities.Entity do
  use App.Entities.EntitySchema

  @doc false
  def changeset(%Entity{} = entity, attrs) do
    entity
    |> cast(attrs, [:title, :type])
    |> validate_required([:title, :type])
  end
end

defmodule App.Entities.TypeA/B do
  use App.Entities.EntitySchema

  @doc false
  def changeset(%TypeA/B{} = entity, attrs) do
    entity
    |> Map.put(:__struct__, Entity)
    |> Entity.changeset(attrs)
    |> put_change(:type, "type_a/b")
  end
end

I prefer this approach, but it still seems to be a bit overkill for a “simple alias”.

3. Define structs

I have not tried this so far but it might be possible to use regular Elixir structs:

defmodule App.Entities.TypeA/B do
  defstruct [:id, :title, :type, :address, :created_at, :updated_at]
end

defmodule App.Entities.Entity do
  # ...

  schema "entities" do
    field :title, :string
    field :type, :string
    has_one :address, Address
  end

  @doc false
  def changeset(%TypeA/B{} = entity, attrs) do
    entity
    |> Map.put(:__struct__, Entity)
    |> changeset(attrs)
    |> put_change(:type, "type_a/b")
  end
  
  def changeset(%Entity{} = entity, attrs) do
    entity
    |> cast(attrs, [:title, :type])
    |> validate_required([:title, :type])
  end
end

This seems to be a clean approach as my %TypeA/B{} structs are pure data containers,
but I’m not sure if I would lose some Ecto functionality, say preloads etc.?

Alternatives, Feedback?

How would you solve this problem and why? Maybe there’s a better approach that I haven’t thought of yet :slight_smile:

Showing Posts 1 to 1

zimt28

zimt28 OP

I’m still not sure how I want to do it, but no. 3 – defining structs – is also possible:

defmodule App.Entities.TypeA/B do
  @entity App.Entities.Entity.__struct__()

  defstruct @entity
            |> Map.keys()
            |> Enum.reduce([], fn key, acc ->
              val = Map.get(@entity, key)
              Keyword.put_new(acc, key, val)
            end)

  def __schema__(key) do
    App.Entities.Entity.__schema__(key)
  end

  def __schema__(key, arg) do
    App.Entities.Entity.__schema__(key, arg)
  end

  def __changeset__ do
    App.Entities.Entity.__changeset__()
  end
end

I’ve moved this into a separate module so I can just do

defmodule App.Entities.TypeA/B do
  use App.Alias, for: App.Entities.Entity
end

— All posts loaded —

Where Next? Top

Trending in Questions Top

water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New
leoschweizer
Hi, we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New

Other Trending Topics Top

budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews