brettbeatty
Central to my app is the Account. I have a lot of schemas that belongs_to Account. I like including corresponding has_one/has_many on Account for query/build_assoc conveniences, but I don’t want to clutter the Account struct with an increasing number of non-core associations that will always be #Ecto.Association.NotLoaded<...>. Is there a way to define an association without adding it to the schema struct?
Off the top of my head the features I would most want but so far have worked around would be these:
join: m in assoc(a, :my_assoc)Ecto.assoc(account, :my_assoc)Ecto.build_assoc(account, :my_assoc)
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
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
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
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
krasenyp
I don’t think there’s a way to do that. But your problem could be a symptom of non-optimal design.
Most probably, the problem is the
Accountschema being central to your app. One solution is to embrace a domain-driven design approach and think of how to separate it in multiple schemas in different bounded contexts. For this you’d have to have deep knowledge of the business domain.Another approach is to stop relying on Ecto schemas everywhere in your app. They’re a database and/or validation concern. You could use well defined maps coupled with specs. Then you’d care more about the shape of your data and non-core fields won’t bother you that much.
I’m sure you’ll find a satisfactory solution.
fuelen
You can hide fields you’re not interested in by defining
InspectprotocolThe code above will hide default
#Ecto.Association.NotLoaded<...>values for:my_assoc1and:my_assoc2fields and will show them only if something else is set.brettbeatty
I appreciated your feedback and ended up going another way, but just to see if what I wanted was technically possible, I made it work in dev by overriding
Account.__schema__/2to support associations that don’t show up in the struct.I have no plans to use this in production, but it does seem to work with
Ecto.assoc(account, :my_assoc),Ecto.build_assoc(account, :my_assoc), andjoin: m in assoc(a, :my_assoc).