Reverse lookup zone not updating
One of the most powerful parts of Django is the automatic admin interface.
These fields should be some kind of text field, such as When somebody does a search in the admin search box, Django splits the search query into words and returns all objects that contain each of the words, case insensitive, where each word must be in at least one of query, because the database only needs to check the beginning of a column’s data, rather than seeking through the entire column’s data.By default, this is set to fields from one or more other fields.The generated value is produced by concatenating the values of the source fields, and then by transforming that result into a valid slug (e.g. Fields are prepopulated on add forms but not on change forms.methods detailed in the previous section, these five methods are in reality designed to be invoked as Django views from the admin application URL dispatching handler to render the pages that deal with model instances CRUD operations.As a result, completely overriding these methods will significantly change the behavior of the admin application.Also, if your search fields include fields that aren’t indexed by the database, you might encounter poor performance on extremely large tables.
For those cases, it’s a good idea to write your own to enable a search box on the admin change list page.
The admin has many hooks for customization, but beware of trying to use those hooks exclusively.
If you need to provide a more process-centric interface that abstracts away the implementation details of database tables and fields, then it’s probably time to write your own views.
For example, you could define a simpler version of the admin form for the to control how many items can appear on a “Show all” admin change list page.
The admin will display a “Show all” link on the change list only if the total result count is less than or equal to this setting.
Note that at this point the parent object and its form have already been saved.