Another idea for the work-around is to add a reload_* association method, e.g., user.reload_profile.
I'm not sure it's worth adding yet another generated association method (or even a good idea), but that would make the reload interface consistent with the build_* and create_* association methods, as I remember them. -Al On Wed, Jul 15, 2015 at 9:45 AM, Prem Sichanugrist <[email protected]> wrote: > DHH wrote: > > > > I'm content with that work-around. I think it's a very rare situation. > Let's make common things easy and uncommon things possible. > > > Alright, I'm sold. Let me submit another PR to deprecate that then. > > > Thank you for your thoughts, everyone. > > -Prem > >> -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
