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
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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).