CODEWITHSUNDEEP
ruby-on-railsdatabase-designactiverecordassociations
js111
js111

Reputation: 1314

Rails DB Schema: new, unique model or just an attribute?

Im working on an Occasion Reminder rails app where users can register then set certain future dates and holidays/occasions that the app will remind them of via email in the future... Also, they can select interests and the emails will contain relevant deals to selected interests on those dates..

Anyways, my question is pretty simple in that I am setting up the initial models for the app and am wondering if the dates/holidays and then the interests should be attributes of the User model/table or unique models of their own (setting a has_many :interests association ect ect in the user model..)

Any ideas or suggestions very welcome!

Thanks much!

Upvotes: 1

Views: 121

Answers (1)

x1a4
x1a4

Reputation: 19475

I would lean toward separate models, especially for the interests. This allows you to easily query for them, and group the results to show various views of your data (e.g. find users with similar interests, or who might be going to the same event on a particular date). Separate models is also the 'correct' answer from a database normalization point of view.

It will be especially useful for your plan to offer deals based on the users' interests.

Upvotes: 2

Related Questions