brettbeatty

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)

Showing Posts 1 to 3

krasenyp

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 Account schema 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

fuelen

You can hide fields you’re not interested in by defining Inspect protocol

@derive {Inspect, optional: [:my_assoc1, :my_assoc2]}

The code above will hide default #Ecto.Association.NotLoaded<...> values for :my_assoc1 and :my_assoc2 fields and will show them only if something else is set.

brettbeatty

brettbeatty OP

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__/2 to support associations that don’t show up in the struct.

  defoverridable __schema__: 2

  def __schema__(:association, :my_assoc) do
    %Ecto.Association.Has{
      cardinality: :one,
      field: :my_assoc,
      owner: __MODULE__,
      related: MyApp.MyContext.MySchema,
      owner_key: :id,
      related_key: :account_id,
      on_cast: nil,
      queryable: MyApp.MyContext.MySchema,
      on_delete: :nothing,
      on_replace: :raise,
      where: [],
      unique: true,
      defaults: [],
      relationship: :child,
      ordered: false,
      preload_order: []
    }
  end

  def __schema__(arg1, arg2) do
    super(arg1, arg2)
  end

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), and join: m in assoc(a, :my_assoc).

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
Onor.io
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
jaybe78
Hello, I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter). The diffic...
New
Trolleger
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New

Other Trending Topics Top

garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
wintermeyer
There are three potential reasons for members of this forum to have a look at https://vutuv.de You are tired or annoyed of LinkedIn. Yo...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews