I was simply referencing “prior art”. The DB simply stores the relevant instance properties - so in this context there is no real difference between a class or a structure.
The challenge isn’t really modelling it in the DB - but determining the best way to exploit that physical data model within Ecto if you need to use changesets because ideally you just want a flat Video, Image, Markdown structure (if you are just querying there is no problem) rather than having to deal with a nested Video, Image, or Markdown struct inside a Media struct.
Ultimately 2.1 Map Hierarchy To A Single Table is the easiest to accomodate within Ecto. Right now I’m not familiar enough with all aspects of Ecto to find the best way to make Map Each Class To Its own Table work - if you need to use changesets.
