It's missing the one solution I see fairly often: a single table with a JSON-typed column that serves as a catch-all dumpster for subtype data. The question an

It's missing the one solution I see fairly often: a single table with a JSON-typed column that serves as a catch-all dumpster for subtype data. The question and answers are from 2010 and the PostgreSQL JSON data type was introduced in 2012, so it makes sense that this rather awful solution hadn't caught on yet. The "NoSQL" movement was just gathering steam in 2010.