Fix cron jobs for pokedex counts and nests #370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(do not use spawnpoint data which is really not required here)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Due to other mapping tools now available, the spawn points are tracked differently and break the current jobs.
This PR fixes this by not using the spawn points table anymore.
Additionally, this gives an enormous performance boost for the jobs due to no more heavy JOINs.
What we currently loose is the start and end times on the nest page.
I need to figure out a new way how to calculate them.
How Has This Been Tested?
Tested on own instance with standard RM DB.
Types of changes