Elixir & Phoenix: Scalable Backend Development · 课时

关联与嵌入式模式

使用 Ecto 关联处理不同数据模型之间的关系,并通过嵌入式模式直接嵌入数据。

第 3 / 4 课11 个步骤

关联与嵌入式模式 是 CoddyKit 上的免费 Elixir & Phoenix: Scalable Backend Development 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Elixir & Phoenix: Scalable Backend Development 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Elixir & Phoenix: Scalable Backend Development 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

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!

免费开始

用 AI 导师学习 Elixir — 免费

在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。

课程
12
课程
48

常见问题解答

「关联与嵌入式模式」课时是免费的吗?

是的 — 「关联与嵌入式模式」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Elixir & Phoenix: Scalable Backend Development 课程的其余内容,请升级到 CoddyKit PRO。 Elixir & Phoenix: Scalable Backend Development 课程共包含 4 节课。

「关联与嵌入式模式」这节课中我会学到什么?

使用 Ecto 关联处理不同数据模型之间的关系,并通过嵌入式模式直接嵌入数据。 你通过在浏览器中直接运行的动手代码来练习 Elixir & Phoenix: Scalable Backend Development,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Elixir & Phoenix: Scalable Backend Development 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Elixir & Phoenix: Scalable Backend Development 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。

「关联与嵌入式模式」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Elixir & Phoenix: Scalable Backend Development 课中编写并运行代码吗?

能。每节 Elixir & Phoenix: Scalable Backend Development 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. Ecto 模式与数据库迁移
  2. Repo、Changesets 与查询
  3. 关联与嵌入式模式
  4. 事务与 Ecto.Multi
← 返回 Elixir & Phoenix: Scalable Backend Development