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

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

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

On Mon, Dec 24, 2012 at 5:28 PM, Paul Olivers li...@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