Skip to main content

When to setup associations in Rails db?

Databases • Asked by Javid Freeman
I've always wondered if there is a better way to help database query performance in rails by breaking up tables with lots of columns? Any recommendations would be appreciated.

Does it make more sense to break out columns into another table or keep them in one?

Example: 

Client.name
Client.address
Client.city
Client.state
Client.zip
Client.twitter
Client.facebook
Client.instagram
Client.contact_name
Client.contact_phone
Client.contact_email
etc...

VS

Client.name

has_one :address
Client.address.address
Client.address.city
Client.address.state
Client.address.zip

has_one :social
Client.social.twitter
Client.social.facebook
Client.social.instagram

has_one :contact
Client.contact.name
Client.contact.phone
Client.contact.email



Login or Create An Account to join the conversation.

Subscribe to the newsletter

Join 27,623+ developers who get early access to new screencasts, articles, guides, updates, and more.

    By clicking this button, you agree to the GoRails Terms of Service and Privacy Policy.

    More of a social being? We're also on Twitter and YouTube.