chrisdel101
I’ve spent several days trying to make my this work, connecting my tables using Ecto Association Guide – Ecto v2.2.11
I think Many-to-many associations in phoenix and ecto - #5 by marick might work.
But now my embedded schema is screwing things up. It is not part of the DB, and it only used for the UI, but I think I still need it.
I thought embedded schemas were not supposed to effect the DB? Is there an way around this?
# this works
org = %{name: "Toys R Us", slug: "toys-r-us"}
org_c = Organization.changeset(%Organization{}, org)
org_insert = Repo.insert!(org_c) |> Repo.preload(:employees)
# this does not - error is due to the .preload(:organizations)
emp = %{last_name: "schmo", first_name: "joe", role: "owner", email: "joe@schmo.com", password: "password"}
emp_c = Employee.registration_changeset(%Employee{}, emp)
emp_insert = Repo.insert!(emp_c) |> TurnStile.Repo.preload(:organizations)
# embedded schema doesn't exist in DB
** (Postgrex.Error) ERROR 42703 (undefined_column) column o0.owner_employee does not exist
# schema with embeds
schema "organizations" do
field :email, :string
field :name, :string
field :slug, :string
field :phone, :string
# org has many employees; employees can belong to many organiztions (mostly for owners)
many_to_many :employees, Employee, join_through: "organization_employees"
embeds_one :owner_employee, Employee do
field :first_name, :string
field :last_name, :string
field :_email, :string
field :password, :string, virtual: true, redact: true
end
schema "employees" do
field :first_name, :string
field :last_name, :string
field :role, :string
field :email, :string
field :password, :string, virtual: true, redact: true
field :confirmed_at, :naive_datetime
# org has many employees within the company; employees belongs to many orgs
many_to_many :organizations, Organization, join_through: "organization_employees"
# join table I want to use, but don't know how to use
defmodule Repo.Migrations.OrganizationEmployees do
use Ecto.Migration
def change do
create table(:organization_employees) do
add :organization_id, references(:organizations)
add :employee_id, references(:employees)
timestamps()
end
create unique_index(:organization_employees, [:organization_id, :employee_id])
end
end
Trending in Questions
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
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
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
cevado
you misunderstood what embedded schemas are. they’re a way to describe a structured
jsonb/mapfield.if you don´t have a jsonb column named
owner_employeeyou’d be better creating a virtual field(virutal fields are the ones that doesn’t exist in the db) that is a map.for reference:
chrisdel101
Perhaps I do misunderstand. So these things don’t apply to me? It’s what I thought based on Embedded Schemas — Ecto v3.14.0
I don’t have
owner_employeebut I do have a join table that I’m trying, and failing, to use.dimitarvp
Embedded schemas without being saved to DB are basically a way to parse data by using Ecto constructs, more or less.
But if you start actively using them with other records that hit the DB you’ll have trouble, yeah. Either have them be virtual attributes (where they are used in other schemas) and/or just add them after a
Repo.getand such.cevado
so, there are a few ways to deal with that:
organizationsa virtual one of the type map. being it a map, you can load whatever map you want there, even aemployeestruct loaded from the database.employeesis aowner_employeeyou can actually make it a relation… something likeand you can preload the owner_employee the same way you preload any other relation.
when you use a embedded schema this way inside another schema is always to describe a structured jsonb field.