Open fyliu opened 11 months ago
We need to come up with requirements for what we want to be able to do with a history model. Maybe document it in this issue or create a separate issue for it.
We will definitely create a separate issue for requirements. That issue will be this issue's dependency
I'm trying to figure out why I crossed out the project_status_history
table from requirements. Looks like that table is still part of the schema and needs a history. It could be that I thought it's not something that djang-simple-history
can solve. I think it's still worth keeping it in the list since this is an evaluation issue, to see if it can be satisfied as well.
I'm going to un-cross it.
I updated the Details section with information on whether I think the library can help what that table needs. It turns out that information was at the bottom of the issue description.
Overview
We would like to know if django-simple-history can fulfill our needs of keeping history of certain tables. We can potentially save time and developer efforts. The package automatically keeps track of change history metadata like who made the change.
Details/Requirements
Action Items
ready for dev lead
label.Resources/Instructions