rails--rails/activerecord/test/fixtures/readers.yml

michael_welcome:
  id: 1
  post_id: 1
  person_id: 1
  first_post_id: 2

michael_authorless:
  id: 2
  post_id: 3
  person_id: 1
  first_post_id: 3
Add missing models and fixture git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@3567 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2006-02-10 01:53:34 -05:00			`michael_welcome:`
			`id: 1`
			`post_id: 1`
			`person_id: 1`
Prevent Relation#merge from collapsing wheres on the RHS This caused a bug with the new associations implementation, because now association conditions are represented as Arel nodes internally right up to when the whole thing gets turned to SQL. In Rails 3.2, association conditions get turned to raw SQL early on, which prevents Relation#merge from interfering. The current implementation was buggy when a default_scope existed on the target model, since we would basically end up doing: default_scope.merge(association_scope) If default_scope contained a where(foo: 'a') and association_scope contained a where(foo: 'b').where(foo: 'c') then the merger would see that the same column is representated on both sides of the merge and collapse the wheres to all but the last: where(foo: 'c') Now, the RHS of the merge is left alone. Fixes #8990 2013-01-27 15:31:01 -05:00			`first_post_id: 2`
Make dynamic finders respect the :include on HasManyThrough associations. Closes #10998. [cpytel] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@8890 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2008-02-17 19:14:54 -05:00
			`michael_authorless:`
			`id: 2`
			`post_id: 3`
Prevent Relation#merge from collapsing wheres on the RHS This caused a bug with the new associations implementation, because now association conditions are represented as Arel nodes internally right up to when the whole thing gets turned to SQL. In Rails 3.2, association conditions get turned to raw SQL early on, which prevents Relation#merge from interfering. The current implementation was buggy when a default_scope existed on the target model, since we would basically end up doing: default_scope.merge(association_scope) If default_scope contained a where(foo: 'a') and association_scope contained a where(foo: 'b').where(foo: 'c') then the merger would see that the same column is representated on both sides of the merge and collapse the wheres to all but the last: where(foo: 'c') Now, the RHS of the merge is left alone. Fixes #8990 2013-01-27 15:31:01 -05:00			`person_id: 1`
			`first_post_id: 3`