Скачать или смотреть Resolving the AttributeError in Odoo 14: A Guide to Proper Cursor Management

Discover how to solve the common Odoo 14 `AttributeError: 'tuple' object has no attribute 'cache'` by implementing the correct cursor management in your models.
---
This video is based on the question https://stackoverflow.com/q/66697211/ asked by the user 'Leandro Campos' ( https://stackoverflow.com/u/9328087/ ) and on the answer https://stackoverflow.com/a/66714946/ provided by the user 'Julio Garduño' ( https://stackoverflow.com/u/15435620/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Odoo14 - AttributeError: 'tuple' object has no attribute 'cache'" while evaluating

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving the AttributeError in Odoo 14: A Guide to Proper Cursor Management

As developers working with Odoo, we sometimes face various errors that can hinder our project's progress. One such error that many have encountered is the AttributeError: 'tuple' object has no attribute 'cache'. This error typically arises when there's a misunderstanding around object management and threading within the Odoo framework, especially when dealing with asynchronous operations. In this post, we will explore the root cause of this error and walk you through an effective solution that can save you a lot of headaches.

Understanding the Problem

In a recent scenario, a developer implemented a model for logging (let's call it Log) and a helper class (Helper) to asynchronously gather and register data. The method _job_function in the Log class gets called by a Cron Job. However, while trying to create a log entry, they encountered the dreaded AttributeError when executing the create_log method.

Here's an excerpt from the code that illustrates the issue:

[[See Video to Reveal this Text or Code Snippet]]

During execution, despite checking that the passed values were correct, the method threw an error indicating that a 'tuple' object was being referenced incorrectly. This prompted an investigation into Odoo's mechanics, particularly how it manages object states and database connections in multi-threaded environments.

Analyzing the Root Cause

The core of the issue lies in how Odoo manages database cursors across different threads. When using asynchronous functions, especially with libraries like asyncio, the default cursor from the original thread can lead to inconsistencies and errors when attempting to access Odoo's model methods. In this case, an existing cursor was not compatible with the new threading context created by asyncio, leading to the error.

The Solution: Proper Cursor Management

To resolve the AttributeError, we need to ensure that we create a new cursor before attempting to access Odoo's model methods. Here’s how you can accurately implement the cursor management in your create_log method:

Step-by-Step Implementation

Use the api.Environment.manage() Method: This will help in managing the database environment properly.

Create a New Cursor: Always create a new cursor when working with asynchronous calls to avoid mistakes.

Establish a New Environment: Use the newly created cursor to set an environment that can access the model methods.

Revised create_log Method

Here's how you can rewrite the create_log function:

[[See Video to Reveal this Text or Code Snippet]]

Why This Works

By utilizing a new cursor with the api.Environment context manager:

Thread Safety: Each thread has its own cursor and environment context, eliminating potential conflicts.

Correct Context Access: The async function will correctly reference the new environment while accessing Odoo's models and their methods without encountering attribute errors.

Conclusion

Dealing with asynchronous operations in Odoo can often lead to complex challenges like the AttributeError. By ensuring proper cursor management, you can maintain correct threading practices and avoid errors that impede your development process. Remember to always create new cursors for separate threads, allowing your Odoo applications to run more smoothly and efficiently.

If you ever find yourself stumped with similar errors, revisiting your cursor management practices could be the key to a swift resolution! Happy coding!