Elixir & Phoenix: Scalable Backend Development · Lektion

Relationen und eingebettete Schemas

Verwalten Sie Beziehungen zwischen verschiedenen Datenmodellen mit Ecto-Relationen und betten Sie Daten direkt mit eingebetteten Schemas ein.

Lektion 3 von 411 Schritte

Relationen und eingebettete Schemas ist eine kostenlose Elixir & Phoenix: Scalable Backend Development-Lektion auf CoddyKit. Dies ist Lektion 3 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Elixir & Phoenix: Scalable Backend Development-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Elixir & Phoenix: Scalable Backend Development-Kurs umfasst insgesamt 4 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

Linking Your Data Together

In relational databases, data is often spread across multiple tables to avoid redundancy and ensure data integrity. Associations in Ecto help you define how these different pieces of data relate to each other.

Think of a blog: A user can write many posts, and each post belongs to one user. Ecto allows you to model these relationships directly in your Elixir schemas.

  • Organize related data logically.
  • Simplify querying and data retrieval.
  • Maintain data consistency.

One User, Many Posts

The most common relationship is one-to-many. For example, one User can have many Posts, but each Post belongs to only one User.

In Ecto, you define this using has_many on the "one" side (e.g., User) and belongs_to on the "many" side (e.g., Post). The belongs_to macro also tells Ecto to add a foreign key (like user_id) to the Post's database table.

Coding `has_many` and `belongs_to`

Let's define our User and Post schemas. Notice how has_many and belongs_to link them. The belongs_to macro expects the name of the association and the module of the associated schema.

defmodule MyApp.User do
  use Ecto.Schema
  schema "users" do
    field :name, :string
    has_many :posts, MyApp.Post # A user has many posts

    timestamps()
  end
end

defmodule MyApp.Post do
  use Ecto.Schema
  schema "posts" do
    field :title, :string
    field :content, :string
    belongs_to :user, MyApp.User # A post belongs to one user

    timestamps()
  end
end

Working with Linked Records

Once schemas are defined, you can create records and link them. Ecto allows you to preload associations, fetching related data in a single query to avoid N+1 problems. Here's how you might create a user and posts, then view the user with their posts.

defmodule MyScript do
  # Mock schemas for demonstration (assuming they are defined)
  defmodule User do
    defstruct [:id, :name, :posts]
  end
  defmodule Post do
    defstruct [:id, :title, :content, :user_id]
  end

  def run do
    IO.puts "--- Demonstrating One-to-Many ---"
    # Simulate creating a user
    user = %User{id: 1, name: "Alice"}
    IO.inspect user, label: "Created User"

    # Simulate creating posts linked to the user
    post1 = %Post{id: 101, title: "My First Post", content: "Hello world!", user_id: user.id}
    post2 = %Post{id: 102, title: "Elixir Fun", content: "Learning Elixir!", user_id: user.id}

    # In a real app, you'd use Repo.insert! and Repo.preload
    # To show the concept of preloading, we manually add posts to the user struct
    user_with_posts = %{user | posts: [post1, post2]}

    IO.inspect user_with_posts, label: "User with preloaded posts"
  end
end

MyScript.run()

Multiple Connections: `many_to_many`

Sometimes, records have a many-to-many relationship. For example, a Student can enroll in many Courses, and each Course can have many Students.

Ecto handles this using a join table (or "pivot table"). You define a schema for this intermediate table, and Ecto uses it to manage the connections between the two main schemas with the many_to_many macro.

  • Requires a separate join schema.
  • Connects two schemas where both sides can have multiple related records.
  • Common for tags, roles, or group memberships.

Coding `many_to_many`

Let's define Student and Course schemas, along with a Enrollment join schema. The many_to_many macro is used on both Student and Course, specifying the join schema.

defmodule MyApp.Student do
  use Ecto.Schema
  schema "students" do
    field :name, :string
    many_to_many :courses, MyApp.Course, join_through: MyApp.Enrollment

    timestamps()
  end
end

defmodule MyApp.Course do
  use Ecto.Schema
  schema "courses" do
    field :title, :string
    many_to_many :students, MyApp.Student, join_through: MyApp.Enrollment

    timestamps()
  end
end

defmodule MyApp.Enrollment do
  use Ecto.Schema
  schema "enrollments" do
    # These are foreign keys to Student and Course
    belongs_to :student, MyApp.Student
    belongs_to :course, MyApp.Course

    timestamps()
  end
end

Accessing Many-to-Many Links

Similar to one-to-many, you use Ecto.Repo.preload/2 to fetch associated many-to-many records. Ecto automatically handles querying the join table behind the scenes.

defmodule MyScript.Many do
  # Mock schemas for demonstration
  defmodule Student do
    defstruct [:id, :name, :courses]
  end
  defmodule Course do
    defstruct [:id, :title, :students]
  end
  defmodule Enrollment do
    defstruct [:id, :student_id, :course_id]
  end

  def run do
    IO.puts "--- Demonstrating Many-to-Many ---"
    # Simulate creating a student and courses
    student1 = %Student{id: 1, name: "Maria"}
    courseA = %Course{id: 101, title: "Elixir Basics"}
    courseB = %Course{id: 102, title: "Phoenix Framework"}

    # Simulate enrollments (join table entries)
    _enrollment1 = %Enrollment{student_id: student1.id, course_id: courseA.id}
    _enrollment2 = %Enrollment{student_id: student1.id, course_id: courseB.id}

    # Simulate preloading courses for student1
    student1_with_courses = %{student1 | courses: [courseA, courseB]}

    IO.inspect student1_with_courses, label: "Student with preloaded courses"
  end
end

MyScript.Many.run()

Data Within Data: Embedded Schemas

While associations link separate records, embedded schemas allow you to store structured data directly within a parent record's field. This means the embedded data is not in a separate table but is part of the parent's row.

Use embedded schemas when the nested data only makes sense in the context of its parent and doesn't need to be independently queried or shared.

  • Data stored directly in the parent record.
  • No separate database table or foreign keys.
  • Ideal for simple, dependent nested data like addresses or metadata.

Coding Embedded Schemas

You define an embedded schema using embeds_one or embeds_many within the parent schema. The embedded schema itself uses Ecto.Schema with @primary_key false and @foreign_key_type :binary_id (or false for no ID) as it's not a standalone table.

defmodule MyScript.Embed do
  defmodule Address do
    use Ecto.Schema
    @primary_key false # Embedded schemas don't have their own primary key
    @foreign_key_type :binary_id # Or false if no ID needed at all
    schema "addresses" do # Table name is ignored for embeds
      field :street, :string
      field :city, :string
      field :zip_code, :string
    end
  end

  defmodule Profile do
    use Ecto.Schema
    schema "profiles" do
      field :username, :string
      embeds_one :address, MyScript.Embed.Address, on_replace: :delete # Embeds one address

      timestamps()
    end
  end

  def run do
    IO.puts "--- Demonstrating Embedded Schemas ---"
    # Create a profile with an embedded address
    profile_changeset =
      Ecto.Changeset.change(%Profile{}, %{username: "john_doe"})
      |> Ecto.Changeset.put_embed(:address, %{
        street: "123 Main St",
        city: "Anytown",
        zip_code: "12345"
      })

    # In a real app: Repo.insert!(profile_changeset)
    # Simulate the resulting struct
    profile_with_address = %Profile{
      id: 1,
      username: "john_doe",
      address: %Address{street: "123 Main St", city: "Anytown", zip_code: "12345"}
    }

    IO.inspect profile_with_address, label: "Profile with embedded address"
  end
end

MyScript.Embed.run()

Check Your Understanding

You've learned about Ecto associations and embedded schemas. Let's test your knowledge!

Associations & Embeds: Key Takeaways

Great job! You've mastered how to model relationships in Ecto:

  • One-to-many: Use has_many and belongs_to. The foreign key lives on the belongs_to side.
  • Many-to-many: Use many_to_many with a dedicated join_through schema.
  • Embedded Schemas: Use embeds_one or embeds_many to store dependent, structured data directly within a parent record.
  • Always use Ecto.Repo.preload/2 to fetch associated data efficiently.

These powerful features are fundamental to building robust and well-structured Ecto applications. Keep practicing!

Kostenlos starten

Lerne Elixir mit einem KI-Tutor — kostenlos

Schreibe und führe echten Code in deinem Browser aus, bekomme sofortige Hilfe von einem 24/7 KI-Tutor und setze dein Lernen im Web oder in der App fort.

Kurse
12
Lektionen
48

Häufig gestellte Fragen

Ist die Lektion „Relationen und eingebettete Schemas“ kostenlos?

Ja — der vollständige Text von „Relationen und eingebettete Schemas“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Elixir & Phoenix: Scalable Backend Development-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Elixir & Phoenix: Scalable Backend Development-Kurs umfasst insgesamt 4 Lektionen.

Was lerne ich in „Relationen und eingebettete Schemas“?

Verwalten Sie Beziehungen zwischen verschiedenen Datenmodellen mit Ecto-Relationen und betten Sie Daten direkt mit eingebetteten Schemas ein. Du übst Elixir & Phoenix: Scalable Backend Development mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um Elixir & Phoenix: Scalable Backend Development zu starten?

Keine Vorkenntnisse erforderlich. Elixir & Phoenix: Scalable Backend Development auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 3 von 4.

Wie lange dauert die Lektion „Relationen und eingebettete Schemas“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser Elixir & Phoenix: Scalable Backend Development-Lektion Code schreiben und ausführen?

Ja. Jede Elixir & Phoenix: Scalable Backend Development-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

  1. Ecto-Schema und Datenbankmigrationen
  2. Repo, Changesets und Abfragen
  3. Relationen und eingebettete Schemas
  4. Transaktionen und Ecto.Multi
← Zurück zu Elixir & Phoenix: Scalable Backend Development