More model inheritance mechanisms
Previously, we saw the basic extension of models, called classic inheritance in the official documentation. This is the most frequent use of inheritance, and the easiest way to think about it is as an in-place extension. You take a model and extend it. As you add new features, they are added to the existing model. A new model isn't created.
We can also inherit from multiple parent models, setting a list of values to the _inherit attribute. Most of the time, this is done with mixin classes. Mixin classes are models that implement generic features to be reused. They are not expected to be used directly, and are like a container of features ready to be added to other models.
If, along with _inherit, we also use the _name attribute with a value different from the parent model, we get a new model reusing the features from the inherited one, with its own database table and data. The official documentation calls this prototype inheritance. Here, you take a model...
