Modeling design question (Ruby On Rails)

Question

I am converting a php project into ruby on rails. The previous project used mysql as the database and the rails project will do the same.

In the project there is a concept of a "step", which a course can have many of. A step has 1 of 5 types. (Quiz, Video, Text..etc) Obviously the type of data required for each step is different.

The way it was modeled before is to store all steps in the same table and have a field that holds a serialized php object of the step. I think this is bad for a couple reasons...You can' really query against serialized data, and it makes adding data or changing the structure of an object very hard.

Would it make more sense to model this data in a database instead of objects?

Jakub Hampl · Accepted Answer · 2011-03-01 14:13:46Z

1

Generally yes. Rails has two possible ways to model this:

Single Table Inheritance - Several models inheriting from a common ancestor, stored in the same table. Good if your steps are really similar to each other. Here you would call has_many on the parent model.
Polymorphic associations - the association macros have an option :polymorphic which allows you to have different models in one association (each can have it's own table). I'd go for that if your steps have little in common.

answered Mar 1, 2011 at 14:13

Jakub Hampl

40.7k10 gold badges80 silver badges111 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Chris Muench Over a year ago

I got deeper into this and I don't see how it is polymorphic. stackoverflow.com/questions/5156948/…

Collectives™ on Stack Overflow

Modeling design question (Ruby On Rails)

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related