-
Notifications
You must be signed in to change notification settings - Fork 0
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
Database consolidation support #131
Comments
… entry fields to administrations. En route to #131.
…ed it! Needs more modularization, too. En route to #131.
Ugh forgot to check and see if the ones that I'm looking at are currently valid. :| |
…ill working on other bugs. En route to #131.
Also, the conditional that attempts to consolidate 3 entries will have to be massaged for correct calculation and comparison of the |
After all of this is done we'll have to add filtering for valid entries in applicable locations throughout the code. :| |
Got to make a list of wiped & inserted entries in order to display a status page after completion. |
Trial run (debugging):
Trial run (non-debugging):
|
In order to avoid processing entries that have already been consolidated multiple times, it would be necessary to go back into |
…mit; there is, however, still one bug which will be detailed in the issue comments. En route to #131.
As can be seen in the following debugging output, there is still an unexpected issue causing potential problems here. Other than this, I've finally got the behavior that I've been looking for. This doesn't complete all of the consolidation at once (multiple loops through the entries to consolidate completely may still be necessary), but it's what I'm going to go with for now until I implement a looping structure around this (in a new issue). Debugging output follows:
|
…. Not closing the issue until it's been verified with fresh data, though. En route to #131.
I've broken up the remaining tasks into separate issues. Consolidation is implemented and this issue is getting long. Moving to the other issues now. |
Much the same as this issue already implemented in the mobile app along the same lines, we're going to implement database consolidation for when some of the administrations were implemented over a short period of time and should be consolidated into single entries. I think instead of deleting the aforementioned records, as was originally implemented in the mobile app, we are going to mark them invalid in this case, thus keeping track of the original unconsolidated entries in case they are required for some purpose. I'm actually going to add that feature to the mobile version, as well. Too bad I didn't think of it sooner.
The text was updated successfully, but these errors were encountered: