Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type

[Chr1sG]

Sounds a bit like what’s discussed here

How to best model Hierarchical Types?

I want a “parent Type” of Project, with “sub-types” for Website Project and Brochure Project. The parent Project Type will have things like Tasks relation, Assignments, Due date, etc. The sub-types will have details unique to their project type. What is the best way to model this cleanly? Everything I try has undesirable limitations. related: