Obtaining an empty recordset for a different model
by Daniel Reis, Alexandre Fayolle, Holger Brunn
Odoo Development Cookbook
- Odoo Development Cookbook
- Table of Contents
- Odoo Development Cookbook
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Installing the Odoo Development Environment
- 2. Managing Odoo Server Instances
- 3. Creating Odoo Modules
- 4. Application Models
- Introduction
- Defining the Model representation and order
- Adding data fields to a model
- Using a float field with configurable precision
- Adding a monetary field to a Model
- Adding relational fields to a Model
- Adding a hierarchy to a Model
- Adding constraint validations to a Model
- Adding computed fields to a Model
- Exposing Related fields stored in other models
- Adding dynamic relations using Reference fields
- Adding features to a Model using inheritance
- Using Abstract Models for reusable Model features
- Using Delegation inheritance to copy features to another Model
- 5. Basic Server Side Development
- Introduction
- Defining model methods and use the API decorators
- Reporting errors to the user
- Obtaining an empty recordset for a different model
- Creating new records
- Updating values of recordset records
- Searching for records
- Combining recordsets
- Filtering recordsets
- Traversing recordset relations
- Extending the business logic defined in a Model
- Extending write() and create()
- Customizing how records are searched
- 6. Advanced Server Side Development Techniques
- 7. Debugging and Automated Testing
- Introduction
- Producing server logs to help debug methods
- Using the Odoo shell to interactively call methods
- Using the Python debugger to trace method execution
- Writing tests for your module using YAML
- Writing tests for your module using Python unit tests
- Running server tests
- Using the Odoo Community Association maintainer quality tools
- 8. Backend Views
- Introduction
- Adding a menu item and window action
- Having an action open a specific view
- Adding content and widgets to a form view
- Adding buttons to forms
- Passing parameters to forms and actions: Context
- Defining filters on record lists: Domain
- List views
- Search views
- Changing existing views: View inheritance
- Document-style forms
- Dynamic form elements using attrs
- Embedded views
- Kanban views
- Show kanban cards in columns according to their state
- Calendar views
- Graph and pivot views
- QWeb reports
- 9. Module Data
- 10. Access Security
- 11. Internationalization
- 12. Automation and Workflows
- 13. Web Server Development
- 14. CMS Website Development
- 15. Web Client Development
- 16. Server Deployment
- Index
When writing Odoo code, the methods of the current model are available via self. If you need to work on a different model, it is not possible to directly instantiate the class of that model—you need to get a recordset for that model to start working.
This recipe shows how to get an empty recordset for any model registered in Odoo inside a model method.
This recipe will reuse the setup of the library example in the addon module my_module.
We will write a small method in the library.book model searching for all library.members. To do this, we need to get an empty recordset for library.members.
To get a recordset for library.members in a method of library.book, you need to take the following steps:
- In the
LibraryBookclass, write a method calledget_all_library_members:class LibraryBook(models.Model): # ... @api.model def get_all_library_members(self): # ... - In the body of the method, use the following code:
library_member_model = self.env['library.member'] return library_member_model.search([])
At start up, Odoo loads all the modules and combines the various classes deriving from Model and defining or extending a given model. These classes are stored in the Odoo registry indexed by name. The environment in self.env provides a shortcut access to the registry by emulating a Python dictionary; if you know the name of the model you're looking for, self.env[model_name] will get you an empty recordset for that model. Moreover, the recordset will share the environment of self.
The call to search() is explained in the Searching for records recipe later.
The
Changing the user performing an action and Calling a method with a modified enviroment recipes in Chapter 6, Advanced Server Side Development Techniques, deal with modifying self.env at runtime.
-
No Comment