Скачать или смотреть Resolving Empty QuerySets After Updating Records in ORM Django

Learn how to effectively manage Django QuerySets and resolve issues where updated records lead to empty QuerySets using clear examples and best practices.
---
This video is based on the question https://stackoverflow.com/q/68850533/ asked by the user 'Flupper' ( https://stackoverflow.com/u/9490848/ ) and on the answer https://stackoverflow.com/a/68850809/ provided by the user 'willeM_ Van Onsem' ( https://stackoverflow.com/u/67579/ ) 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: filter on new updated queryset return empty queryset using ORM Django

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.
---
Understanding the Issue: Empty QuerySets After Record Updates

If you're working with Django's ORM (Object-Relational Mapping) and you've ever faced the scenario where your updated QuerySet returns empty results, you're not alone. This issue typically arises when attempting to filter an updated QuerySet, only to find that the results do not match your expectations. Let's break down what happens during this process and how you can efficiently manage your QuerySets to avoid these issues.

What Happens with QuerySets in Django?

When you create a QuerySet in Django, it represents a specific set of items from your database, defined by your filter conditions. In the code example provided:

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

Initially, qs contains BankTransfer instances that have a status of STATUS_NEW. During the first loop, you update each instance's status to STATUS_APPROVED. This action directly modifies the records in your database; however, it's important to remember that a QuerySet is essentially a query template that gets re-evaluated every time you filter it.

The Core Problem: Filtering an Updated QuerySet

After updating the statuses, if you attempt to filter the same QuerySet:

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

Here lies the confusion: You are performing a new query that looks for BankTransfer items with both status=STATUS_NEW and a related purpose__status being pending_completed. Since you've just changed the status to STATUS_APPROVED, no records will fit that filter anymore, resulting in an empty QuerySet.

An Effective Solution: Reorder Your Process

To solve this issue, you should update the records while filtering in the correct order. Here’s a refined version of the code that correctly updates the statuses without running into the empty QuerySet issue:

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

Using Bulk Updates for Efficiency

Instead of looping through the QuerySet to update each object individually, you can improve performance by using Django's update() method to apply changes in bulk. Here’s how you can achieve this:

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

This method updates the necessary records in the database directly with a single SQL query, which is both optimal and efficient.

Conclusion

Managing QuerySets effectively within Django requires an understanding of how filtering and updating interact. By recognizing that a QuerySet represents a dynamic database query, you can avoid the common pitfall of having empty results after updates. Always remember to structure your processing sequence wisely and leverage bulk updates when possible for enhanced performance. Happy coding!