[Rails] Re: Strange behaviour with ActiveRecord has_many collections, Rails 4 compared to Rails 3

Hi Fred,

Thanks for your reply.

"Using new in this way isn't something I've come across in quite a few years of using rails."

How would you initialise a new Task object given you have the @story instance available to you?

@task = Task.new(:story_id => @story.id)    ?

If the above, I really don't see the point of the new and build methods for a has_many association...

For a has_one association, I would be able to do:

@task = @story.build_task

So it makes no sense, that @task = @story.tasks.build doesn't do the same thing... As 'build' seems to just be an alias of 'new'.

Thanks.

On Monday, 21 October 2013 13:23:54 UTC+1, Frederick Cheung wrote:

On Monday, October 21, 2013 11:28:22 AM UTC+1, Neil Williams wrote:

Hi All,

I have been told to post discussion based topic on here instead of the GitHub Issues.

I thought this 'could' be a bug, but just need some clarification really. The issue I posted is here, does anyone have any thoughts?

Again: https://github.com/rails/rails/issues/12597

Thanks a lot.

To be honest it feels to me like what you were using just happened to work by accident, because by default method_missing on the association sets up a scope and calls the method on the class. If this was indeed accidental behaviour then the change could well be the side effect of another change. Using new in this way isn't something I've come across in quite a few years of using rails.

Fred

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a2da6d12-383d-48d4-bf41-3306ce2c7e5e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.