-
Notifications
You must be signed in to change notification settings - Fork 106
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
db query bugfix #202
base: devel
Are you sure you want to change the base?
db query bugfix #202
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As before... well caught, this is really not correct for a |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That sounds quite reasonable, considering that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused by this change. 🤔
According to the comment, the decision to use
GROUP BY
instead ofORDER BY
is deliberate, for performance reasons. But you seem to have reverted toORDER BY
instead. I wonder why? Was the previously existing query giving errors — or not finding the expected results?I'm just really asking for curiosity's sake, I have no way to accept or reject your PR anyway! 😹
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the issue is related to
I think the fix should have been.