MatijaL
Hi guys,
I’m trying to build something similar to Twitter where users can follow other users. I’m not sure exactly how to properly create self-referencing schema in this case.
Migrations:
defmodule MyApp.Repo.Migrations.CreateUsers do
use Ecto.Migration
def change do
create table(:users) do
add :username, :string
end
end
end
defmodule MyApp.Repo.Migrations.CreateFollows do
use Ecto.Migration
def change do
create table(:followings) do
add :follower_id, references(:users, on_delete: :delete_all)
add :followed_id, references(:users, on_delete: :delete_all)
timestamps()
end
create index(:followings, [:follower_id, :followed_id], unique: true)
end
end
Schemas:
defmodule MyApp.User do
use Ecto.Schema
schema "users" do
field :username, :string
...
end
end
defmodule MyApp.Follow do
use Ecto.Schema
schema "followings" do
---
end
end
Can someone help me write the schemas properly using many_to_many please?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tfwright
Did you try following this example in the docs? Basically it’s just a normal schema that you pass to the
join_throughoption ofmany_to_manyinstead of the table name directly. Although it’s maybe worth noting that you don’t need to use a join schema. Personally I often prefer to avoid dealing with non-intuitive concept names like a “Follow”…MatijaL
I did check those pages abut I’m not entirely sure which approach even to take as it’s the self-referencing schema.
tfwright
What part of the self-referencing is causing you problems?
MatijaL
To be honest, I don’t even know… I also don’t like those abstract names, what do you think about a table called “followings” with “user_id” and a “follower_id”?