Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Ruby Active Record Associations in Rails Active Record Associations Has One Associations

Why we use "user.create_profile" to create a profile instead of "user.profile.create"? The latter doesn't work, but why?

I am curious why we don't use "user.profile.create"? Why we use "user.create_profile"?

1 Answer

Steven Parker
Steven Parker
210,475 Points

One issue is that the profile doesn't have a "create" method to call. But even if it did, before the profile is created, "user.profile" has a value of "nil", so you would not have access to any methods on it yet. So it makes sense for "create_profile" to be a separate method.