Book Image

Odoo 11 Development Essentials - Third Edition

By : Daniel Reis
Book Image

Odoo 11 Development Essentials - Third Edition

By: Daniel Reis

Overview of this book

Odoo continues to gain worldwide momentum as the best platform for open source ERP installations. Now, with Odoo 11, you have access to an improved GUI, performance optimization, integrated in-app purchase features, and a fast-growing community to help transform and modernize your business. With this practical guide, you will cover all the new features that Odoo 11 has to offer to build and customize business applications, focusing on the publicly available community edition. We begin with setting up a development environment, and as you make your way through the chapters, you will learn to build feature-rich business applications. With the aim of jump-starting your Odoo proficiency level, from no specific knowledge to application development readiness, you will develop your first Odoo application. We then move on to topics such as models and views, and understand how to use server APIs to add business logic, helping to lay a solid foundation for advanced topics. The book concludes with Odoo interactions and how to use the Odoo API from other programs, all of which will enable you to efficiently integrate applications with other external systems.
Table of Contents (20 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

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...