Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we store a history of when each mouse was in each cage? #55

Open
cxrodgers opened this issue Jun 4, 2016 · 3 comments
Open

Should we store a history of when each mouse was in each cage? #55

cxrodgers opened this issue Jun 4, 2016 · 3 comments

Comments

@cxrodgers
Copy link
Owner

When we make a change, is the previous state of the database stored somewhere? Certainly this information is available in our daily database backups, but this is not the most convenient way to get a history of when every mouse was in every cage.

@cxrodgers cxrodgers changed the title Are we storing a history of when every mouse was in every cage? Should we store a history of when each mouse was in each cage? Jul 3, 2016
@cxrodgers
Copy link
Owner Author

No, pretty sure this information is not stored. I think there is a simple revision history stored in admin "recent actions" widget, but probably not complete.

However, it's not clear how exactly this would be implemented, and it could get complicated (especially if someone accidentally chooses the wrong cage from the drop-down, and then fixes it).

@cxrodgers
Copy link
Owner Author

@cxrodgers
Copy link
Owner Author

There is a log of changes in django.contrib.admin.models.LogEntry.objects.all() but it doesn't have the actual data (ie, which cage), it just says that the mouse's cage (or whatever) was changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant