Change resource specs aggregation to better handle joins to modw.resource_allocated table #1837
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.
The previous join to
modw.resource_allocated
relied on the fact that in Open XDMoD the start and end dates for a resource spec and resource allocated are the same. This is not the case for ACCESS XDMoD so this change instead joins using a date range to get an change in the resource allocated during the date range being allocated. The start and end dates frommodw.resource_allocated
are also used in the macro used to determine the time period used in calculating the various columns.Tests performed
Tested in docker and added an extra rows to
modw.resourcespecs
andmodw.resource_allocated
to check that the new aggregation works. Below is a sql file that has an export of those tables with the extra rows that can be used to manually test that the aggregation works.resourcespecs_sql_dump.zip
Checklist: