Should I use has_one or belongs_to in ruby on rails?

ruby-on-rails belongs-to has-one
Satchel picture Satchel · Jul 10, 2010 · Viewed 23k times · Source

I want to have a Status model which will be relatively static after some user-defined set up (and different users may have different values on status).

The status can apply to different models, such as Contact and Event.

so the statuses returned by contact.status will be different from event.status

I want to design the app so that status table has different types (contacts and events).

What is the right strategy and format for this?

I am thinking of declaring :has_one Status in the Contact model, and storing a :status_id in the :contacts table. Ditto with Event.

:statuses table will have the status value, type, and date.

does this make sense? Can you suggest a better approach?

Answer

theIV picture theIV · Jul 10, 2010

There is a guide on this very question. Your situation is slightly different in that it seems as though your Status model really needs to be polymorphic since different things will be 'statusable'.

To answer your question, Contact/Event has_one Status does make sense to me.

Related questions

Rails: has_one and belongs_to with presence validation on both foreign keys

I have an application with a users table and a user_profiles table. A user has_one user profile and a user profile belongs_to a user. I want to make sure that the association scenario is always true, so …

Read More
Rails has_one and belongs_to migration?

I'm trying to establish a relationship between two models in Rails but I am having trouble figuring out what I need to do in my migration. Any help is much appreciated. I want each business to have a type/category …

Read More
Validation failed Class must exist

I have been (hours) trouble with associations in Rails. I found a lot of similar problems, but I couldn't apply for my case: City's class: class City < ApplicationRecord has_many :users end User's class: class User < ApplicationRecord belongs_…

Read More