Most of the times, Aggregates that fall under this Indicator are actually pretty simple Queries that filter by an Id, mostly the Primary Key of an Entity. In which case, the Max. Records is really not needed, making this Indicator more annoying than helpful.
+1
Hello João,
We will evaluate if we can make the finding more intelligent to avoid this "false positives".
Kind regards
Hi,
In the performance report inside "Unlimited records in aggregate" category are being shown false positives when we have a filter by the primary key of a table.
If we are doing a filter by primary key it will return at max 1 result so we don't need to use the max records. These issues are false positive and should be hidden from the report. We spent lots of time dismissing these ones instead of work in real ones.
Best regards.
We are working on improving this pattern, and this part of querying by id is one of the improvements.
We intend to minimize false positives, and maximize valuable actionable items.
Thank you for your feedback.