Django: When to customize save vs using post-save signal

by

I generally use this rule of thumb:

  • If you have to modify data so that the save won’t fail, then override save() (you don’t really have another option). For example, in an app I’m working on, I have a model with a text field that has a list of choices. This interfaces with old code, and replaces an older model that had a similar text field, but with a different list of choices. The old code sometimes passes my model a choice from the older model, but there’s a 1:1 mapping between choices, so in such a case I can modify the choice to the new one. Makes sense to do this in save().
  • Otherwise, if the save can proceed without intervention, I generally use a post-save signal.

More Related Contents:

  1. How to store a dictionary in a Django database model’s field
  2. Does the django-rest-framework provide an admin site to manage models?
  3. Django dynamic model fields
  4. How to convert JSON data into a Python object?
  5. Django filter queryset __in for *every* item in list
  6. How to execute a Python script from the Django shell?
  7. Django, creating a custom 500/404 error page
  8. Django: Redirect to previous page after login
  9. How do I force Django to ignore any caches and reload data?
  10. Django: Adding “NULLS LAST” to query
  11. Serving dynamically generated ZIP archives in Django
  12. Django Rest Framework writable nested serializers
  13. How can I save my secret keys and password securely in my version control system?
  14. get request data in Django form
  15. How do I use Django templates without the rest of Django?
  16. many-to-many in list display django
  17. Calling a REST API from django view
  18. Django – makemigrations – No changes detected
  19. Class has no objects member
  20. How to escape {{ or }} in django template?
  21. Django 1.11 TypeError context must be a dict rather than Context
  22. How do I filter values in a Django form using ModelForm?
  23. Django cannot import login from django.contrib.auth.views
  24. Django ConnectionAbortedError: [WinError 10053] An established connection was aborted by the software in your host machine
  25. Running a specific test case in Django when your app has a tests directory
  26. Change a Django form field to a hidden field
  27. Making django server accessible in LAN
  28. Django Admin: Using a custom widget for only one model field
  29. Generic many-to-many relationships
  30. Embedding a Plotly chart in a Django template

Leave a Comment