Re: [Rails] Bad idea to add/remove associations in after_find

On Mon, Dec 24, 2012 at 5:28 PM, Paul Olivers <lists@ruby-forum.com> wrote:
> I have 2 distinct types of users (artists and curators) in my system and
> they currently share all associations (eg has_one :portfolio).
> However, a curator shouldn't have a portfolio so I would like to only
> add that association when required. Obviously I could just return nil
> for that method, but it doesn't feel right having that there in the
> first place.
>
> What's the best way to get around this? I've looked at using eval in
> after_find to call the has_one, but couldn't get it working.
>
> Any thoughts?

Can an artist also be a curator?

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.