New and updated queries for KUI #158
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
hexylena
approved these changes
Jun 7, 2024
| @@ -2452,7 +2523,7 @@ query_monthly-users-registered(){ ##? [--year=<YYYY>] [--month=<MM>] [--by_group | |||
|
|
|||
| read -r -d '' QUERY <<-EOF | |||
| SELECT | |||
| TO_CHAR(date_trunc('month', galaxy_user.create_time AT TIME ZONE 'UTC')::DATE, 'YYYY-MM') AS month, | |||
| TO_CHAR(date_trunc('month', galaxy_user.create_time)::DATE, 'YYYY-MM') AS month, | |||
There was a problem hiding this comment.
someone else added a timezone cast recently, I think I need to go through all of these and identify a policy (probably "don't AT TZ, fix your db") but that's a task for me for later.
|
Thanks for the review and the merge. |
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.
Added a few queries to count number of datasets, histories, workflows, and workflow invocations as well as updated a few existing ones. Without these updates, when filtering by a given month, the queries were returning values spanning two months.