Скачать или смотреть Prevent Django Admin List View from Using Choices Lookup

Learn how to streamline your Django admin list view by preventing expensive choices lookups while displaying account numbers effectively.
---
This video is based on the question https://stackoverflow.com/q/64455809/ asked by the user 'James Lin' ( https://stackoverflow.com/u/342553/ ) and on the answer https://stackoverflow.com/a/64456291/ provided by the user 'JPG' ( https://stackoverflow.com/u/8283848/ ) 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: Django admin list view prevent choices lookup

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.
---
Streamlining Django Admin: Preventing Choices Lookup in List View

When working with Django's admin interface, you may encounter scenarios where you want to display certain fields in a list view without triggering expensive lookups. One such case arises when you are using a field with choices. In this guide, we will address how to prevent Django’s admin list view from evaluating these choices and thereby avoid costly operations when loading your admin pages.

The Issue: Choices Lookup in List View

In Django, when you specify list_display in a model admin class, Django attempts to fetch the display values by evaluating the iterable of choices associated with that field. This evaluation can be very resource-intensive. For example, here's a simplified version of a model and its admin configuration:

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

In the above example, when you load the admin list view for CustomerProfile, Django will evaluate CustomerChoices, triggering the expensive lookup unnecessarily.

Solutions: What Can You Do?

To handle this situation, you have two primary choices:

Display the Stored Value Directly

Keep Existing Choices Functionality (Not Recommended for Performance)

Solution 1: Display the Stored Value Directly

To effectively display the account number without triggering the expensive choices lookup, you can create a custom list method in your model admin. Here is how you can do this:

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

In this example, the account_number_dup method simply returns the raw account_number from the database, avoiding the need to evaluate the choice display.

Solution 2: Keep Existing Choices Functionality

While you could choose to do nothing and keep the choices setup as is, this approach can lead to slow response times in environments with larger datasets due to the expensive lookups triggering for each admin list page load. Hence, this solution is generally not recommended unless absolutely necessary.

Conclusion

By using a custom method to retrieve the account number directly from the database, you successfully streamline the Django Admin List View, preventing unnecessary expensive lookups and improving the performance of your application. Adopting this approach not only enhances the admin experience but also keeps your application efficient and responsive.

The next time you find yourself in a similar situation, remember the simple trick of creating custom list methods that return the data you really need without the overhead of choice evaluations!