search for: content_type_new

...w, article, etc. Content_type was not mandatory, but it allowed later to "deactivate" types of contents, for example. So then Content stored the common attributes/properties between the different content types (creation date, owner_id, etc). For each content type, there was a model i.e: Content_type_new Content_type_article ... Rails speaking, Content has_one Content_type_new, has_one Content_type_article, etc. So for each Article, there was a record in ''content'' table and another in ''content_type_article''. This approach makes more sense to me than having a uni...