fix(web): Use limit() instead of tail() for fetching recent SMART entries #14
Conversation
This file contains hidden or 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
…fetching recent entries - Updated the aggregation logic in `aggregateSmartAttributesQuery` to utilize `limit()` for retrieving the newest entries after sorting, ensuring correct data retrieval. - Adjusted subquery construction to improve clarity and maintainability. - Enhanced comments for better understanding of the changes made. (cherry picked from commit c1f70ff)
Owner
Author
Merged to Fork (2025-11-30)Cherry-picked into Starosdev/scrutiny. Changes Made
Thanks for the contribution. |
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.
Summary
Fix smart attributes query to use limit() instead of tail() for fetching recent entries, improving query performance.
Origin
Cherry-picked from upstream PR: AnalogJ#829
Original author: @jianyun8023
Changes
Closes #2