Rails ActiveRecord 关联更新不一致

Question

我遇到了一些我不理解的 Rails 2.3.5 ActiveRecord 行为。对象的关联 ID 似乎可以以不一致的方式更新。

通过一个示例可以最好地解释这一点：

使用字符串属性 'title' 创建一个 Post 模型，并使用字符串属性 创建一个 Comment 模型>'内容'。

以下是关联：

class Post < ActiveRecord::Base
  has_many :comments
end

class Comment < ActiveRecord::Base
  belongs_to :post
end

场景 #1：在以下代码中，我创建一个带有关联 Comment 的 Post，通过 创建第二个 Post >找到'第一个，将第二个Comment添加到第一个Post并发现第二个Post有第二个< code>Comment 与其关联，无需显式分配。

post1 = Post.new
post1 = Post.new(:title => 'Post 1')
comment1 = Comment.new(:content => 'content 1')
post1.comments << comment1
post1.save
# Create a second Post object by find'ing the first
post2 = Post.find_by_title('Post 1')
# Add a new Comment to the first Post object
comment2 = Comment.new(:content => 'content 2')
post1.comments << comment2 
# Note that both Comments are associated with both Post objects even
# though I never explicitly associated it with post2.
post1.comment_ids # => [12, 13]
post2.comment_ids # => [12, 13]

场景 #2：再次运行上述命令，但这次插入一个额外的命令，从表面上看，该命令不会影响结果。额外的命令是 post2.comments，它发生在创建 comment2 之后以及添加 comment2之前 > 到 post1。

post1 = Post.new
post1 = Post.new(:title => 'Post 1A')
comment1 = Comment.new(:content => 'content 1A')
post1.comments << comment1
post1.save
# Create a second Post object by find'ing the first
post2 = Post.find_by_title('Post 1A')
# Add a new Comment to the first Post object
comment2 = Comment.new(:content => 'content 2A')
post2.comments # !! THIS IS THE EXTRA COMMAND !!
post1.comments << comment2 
# Note that both Comments are associated with both Post objects even
# though I never explicitly associated it with post2.
post1.comment_ids # => [14, 15]
post2.comment_ids # => [14]

请注意，在此场景中只有一条评论与 post2 关联，而在场景 1 中则有两条评论。

大问题：为什么在将新的 Comment 添加到 post1 之前运行 post2.comments 会对与 关联的评论产生任何影响发布2？

Answer 1

这与 Active Record 缓存请求的方式以及处理 has_many 关联的方式有关。

除非在查找过程中使用 :include 选项预先加载关联。在需要之前，Rails 不会填充找到的记录的关联。当需要关联时，会进行一些记忆来减少执行的SQL查询数量。

单步执行问题中的代码：

post1 = Post.new(:title => 'Post 1')
comment1 = Comment.new(:content => 'content 1')
post1.comments << comment1  # updates post1's internal comments cache
post1.save 

# Create a second Post object by find'ing the first
post2 = Post.find_by_title('Post 1') 

# Add a new Comment to the first Post object
comment2 = Comment.new(:content => 'content 2')
post1.comments << comment2   # updates post1's internal comments cache

# Note that both Comments are associated with both Post objects even
# though I never explicitly associated it with post2.
post1.comment_ids # => [12, 13]

# this is the first time post2.comments are loaded. 
# SELECT comments.* FROM comments JOIN comments.post_id = posts.id WHERE posts.id = #{post2.id}
post2.comment_ids # => [12, 13]

场景 2：

post1 = Post.new(:title => 'Post 1A')
comment1 = Comment.new(:content => 'content 1A')
post1.comments << comment1
post1.save

# Create a second Post object by find'ing the first
post2 = Post.find_by_title('Post 1A')

# Add a new Comment to the first Post object
comment2 = Comment.new(:content => 'content 2A')

# first time post2.comments are loaded. 
# SELECT comments.* FROM comments JOIN comments.post_id = posts.id WHERE 
#   posts.id = post2.comments #=> Returns one comment (id = 14)
# cached internally.

post1.comments << comment2 
# Note that both Comments are associated with both Post objects even
# though I never explicitly associated it with post2.
post1.comment_ids # => [14, 15]

# post2.comment has already been cached, so the SQL query is not executed again.

post2.comment_ids # => [14]

NB post2.comment_ids 内部定义为 post2.comments.map(&:id)

PS 我对 这个问题可能有帮助你明白为什么 post2 尽管你没有碰过它却被更新了。