django-field-history
django-field-history copied to clipboard
A Django app to track changes to model fields.
Hi. There is a problem with Models which have primary key with default=uuid ``` id = models.UUIDField(default=uuid.uuid4, editable=False, primary_key=True) ``` The initial/first field history value is not saved to database....
We had an issue in https://github.com/twschiller/open-synthesis/issues/214 where we'd get a database integrity error about the FieldHistory referencing users that didn't exist We had to add the following to our base...
I needed a way to have a "post_save" signal that was triggered after FieldHistory instances where created. This implementation is working fine for what I needed. I have to note...
$ ./manage.py createinitialfieldhistory Traceback (most recent call last): File "src/manage.py", line 10, in execute_from_command_line(sys.argv) File "/home/vagrant/mdm/env/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/home/vagrant/mdm/env/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/vagrant/mdm/env/local/lib/python2.7/site-packages/django/core/management/__init__.py",...
I'm not certain if this was exclusive to django-configurations, but setting FIELD_HISTORY_OBJECT_ID_TYPE = models.IntegerField caused it to error out because an instance of the class was being passed, not the...
I would like to rename the field "status" to "portal_status" in my app. Originally this is what it looks like:  I executed `python manage.py renamefieldhistory --model=accounts.account --from_field=status --to_field=portal_status` and...
Currently the FieldHistory model shows up in the admin as 'Field historys', so this changes it to 'Field histories'
Not a huge problem but it would be good to have the installation and quickstart sections of the docs mention that you need to run `manage.py migrate` after adding 'field_history'...
This does not work, if object representation have type `unicode`: ```python return '{} field history for {}'.format(self.field_name, self.object) ``` fix for python 2.7: ```python return u'{} field history for {}'.format(self.field_name,...
In postgresql there is specific and optimized field for JSON, jsonb which can permit the direct used of the json object (and i guess that other dbb has his own)....