With regards to the history log on models in the admin view. I am adding instances of models via the db api (model.save()) method. When such a model is opened (but not edited) and then saved for the first time in the admin model view a history log entry is created showing ALL elements of the model has changed. After this you can open and save the model and the history log behaves as expected.
I looked into the code and see the has_changed and changed_data dict is created by calling methods on widgets which takes the responsibility to compare "new" data with "initial" data. Unless I am mistaken these widgets think the initial data differs from the committed (but unchanged) data. I now need to look deeper but hoped somebody stumbled across something similar that would be willing to offer help? Expected behavior would be that the history log on first model save (from the admin model view) only show model elements that actually changed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
