The current suggestion is to steer away from the serialized data column, and go for a muti-table system. One table is content_blocks, which has a polymorphic relationship to the model/table of its specific type.

I'd love more conversation!

I think you're looking for EAV (Entity Attribute Value) design.

adamgoose said:

The current suggestion is to steer away from the serialized data column, and go for a muti-table system. One table is content_blocks, which has a polymorphic relationship to the model/table of its specific type.

I'd love more conversation!

This is how I would approach it.

moon0326 said:

I think you're looking for EAV (Entity Attribute Value) design.

I think this might be overkill in this situation. With my experience with EAV I'd avoid it until you are sure its necessary.

Not saying its a bad suggestion. Just might not be the simplest.

Yes, I totally agree. If it can be done in a simpler way, I would not bother to use EAV due to its performance issue.