Search for a command to run...
Made my first website in Microsoft Word at age 13, when I discovered the "save as html" button. Since then I've journeyed various computing languages, eventually settling for Python. I love diving into the core of my favorite framework - Django - discover and writing about new stuff.
Django offers a great deal of hidden functionality - secret gems - if you know where to look. In this serie I am showing tips and tricks to get the most out of Django.
When using the requests library in Python you can use some built-in auth mechanisms like HTTPBasicAuth and HTTPDigestAuth. However, I could not find any package that allows doing a simple JSON Web Token (JWT) authentication, so I decided to make a sn...
When working in the Django admin with a lot of users, you might sometimes want to offer the functionality to users to choose which columns they want to see in the changelist page. For some users some columns might be more relevant than to others. One...
Expiring a superuser in Django after a due date
At Wundermart we started saving monetary amounts in Django, we naively started with DecimalField(decimal_places=2) for our financial data. After some time we realized that you will lose data this way when applying calculations, for example: €100 * 0....
Suppose you change your Django model instance, how do you know if the data actually changed? There are a few ways to achieve this, for example using django-simple-history which will add a database entry for every change to keep history. However, you ...
The django-simple-history package is awesome as it shows you all the activity on a certain Django model object. It allows seeing how it was mutated over time and who changed it. However, there is one caveat: you cannot easily see what objects were deleted as there is simply no direct reference anymore.
The problem had already been raised with some solutions already been provided, but these mainly focus on providing a filter to make them visible. The Gist below adds a new history page on the model's change list page. The benefit here is that you can override the BaseHistoryAdmin to add for example filters or search functionality, that you would not have normally.
For example, to combine Django Simple History with DjangoQL you can add advanced searching like this:
from django.contrib import admin
from djangoql.admin import DjangoQLSearchMixin
class SomeHistoryAdmin(DjangoQLSearchMixin, BaseHistoryAdmin):
# Add your specific DjangoQL settings here
...
class SomeModelAdmin(WMSimpleHistoryAdmin):
history_admin = SomeHistoryAdmin
# The rest of your model settings
...
admin.site.register(SomeModel, SomeModelAdmin)
For adding additional filters to the history admin you could do something similar by specifying SomeHistoryAdmin.list_filter, by default it's already filtered on history_type so you can quickly identify which objects were added, changed or deleted.
This example shows how to use DjangoQL to query orders that were deleted. By adding templates/admin/change_list.html a button will be created on all model change list pages just before the regular Add button, it will refer to the history page. Beware that this also adds a button on admin pages that are not based on WMSimpleHistoryAdmin.
Go ahead and tweak the Gist to your own needs: