Overview
Review query-like calls directly inside loops and measure actual receiver behavior, query count and workload. The static candidate does not prove a performance defect.
Why it Matters
Repeated query-like calls may increase work with loop size; measure actual behavior before concluding impact.
Interpret the reported resource and collection scope before making changes. Unsupported source, unresolved symbols and bounded collection gaps cannot establish a clean result.
Verification Steps
Manual Verification
- Review query-like calls directly inside loops and measure actual receiver behavior, query count and workload. The static candidate does not prove a performance defect.
- Inspect the reported file, declaration, package or evidence record in the same selected release. Keep source observations separate from effective runtime behavior.
- Apply the rule-specific remediation below, validate the affected behavior in staging, and rerun the same selection.
Command / Review Sample
php magebean.phar audit --path=/var/www/magento --profile=module-reliability --rules=MB-0827 --modules=Vendor_Module
Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.
Remediation / Fix Guidance
- Review the reported declaration or source location in context.
- Validate the affected lifecycle or operational behavior in staging.
- Rerun MB-0827 against the same release, profile and relevant file/key/package scope; compare the new evidence and inspect any independent collection gaps.
Examples
Illustrative declaration/review examples, not recorded scan output. A pass example concerns only the stated predicate and supported collected scope.
Fail Example
foreach ($ids as $id) { $connection->query($sql); }
Pass Example
// Review and use a bounded bulk operation where semantics allow.
$bulkReader->readIds($ids);
// No direct loop-query pattern here; inspect implementation and measure separately.
Scope and Evidence Limits
Rule revision: 1. Target modes: LOCAL.
Record query-like method calls directly inside loops in selected module PHP for performance review.
Bounded static analysis. Runtime setup, handler dispatch, failure behavior and performance are outside the supported predicate.
Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.