Programming Ecto

Approach #2: Using an Abstract Schema

This approach might not be completely intuitive at first glance, but it’s worth exploring as it reveals some interesting features about schemas that we haven’t looked at before, and might be the right solution for your app.

With this approach, we’ll create separate notes tables for each of the other tables we’re associating with. So we’ll have one notes table for artists, another for albums, and so on. Here’s how we might write the migration:

priv/repo/migrations/20180620125250_add_notes_tables.exs

create table(:notes_for_artists) do
  add :note, :text, null: false
  add :author, :string, null: false
  add :assoc_id, references(:artists)
  timestamps()
end