You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have an application that uses django-simple-history, and I'm considering replacing it with django-auditlog. In django-simple-history there is a TextField called history_change_reason which I use to provide additional context on the changes made (e.g., "Quantity increased at the request of John Doe").
I understand that in projects using v2 of django-auditlog, the changes_text field was used to store JSON, while in v3, it uses the changes JSONField. I was thinking of storing the history_change_reason inside the changes_text field, but I'd like to know if the changes_text field is suitable.
Can someone explain the purpose of the changes_text field in v3, or if it is temporary and will be removed in a future release? Thank you!
I currently have an application that uses django-simple-history, and I'm considering replacing it with django-auditlog. In django-simple-history there is a
TextField
calledhistory_change_reason
which I use to provide additional context on the changes made (e.g., "Quantity increased at the request of John Doe").I understand that in projects using v2 of django-auditlog, the
changes_text
field was used to store JSON, while in v3, it uses thechanges
JSONField. I was thinking of storing thehistory_change_reason
inside thechanges_text
field, but I'd like to know if thechanges_text
field is suitable.Can someone explain the purpose of the
changes_text
field in v3, or if it is temporary and will be removed in a future release? Thank you!This may also help address the question in #647.
The text was updated successfully, but these errors were encountered: