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

Automatic cleanup of reportdb #118

Closed
kokx opened this issue Sep 2, 2015 · 1 comment
Closed

Automatic cleanup of reportdb #118

kokx opened this issue Sep 2, 2015 · 1 comment

Comments

@kokx
Copy link
Contributor

kokx commented Sep 2, 2015

Right now, members and decisions will be added to the reportdb. However, they will not be removed. The easiest way to solve this (and possible errors) is to simply TRUNCATE all the tables in the reportdb every time.

This means that between 0:30 and 2:00, the secretary cannot run queries in the report database. Possibly, this should be adjusted as well, or guarded in some way.

@tomudding
Copy link
Member

There is currently no reason to implement something like this, as most updates to the entities are propagated (though not everything, see for example #147). Furthermore, completely regenerating the report database will cause foreign key constraint failures in GEWISWEB as the ids of organs shift (or change).

@tomudding tomudding closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2022
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

2 participants