Browse Source
- Mark force-added entity-field filter mappings as ignored under OR so EntityDataAdapter keeps the response shape identical to AND (applied to both findEntityDataByQuery and validateEntityCountQuery paths). - Skip the ON-clause filter in toLatestJoin when forceLeftJoin=true to avoid duplicating the predicate that buildQuery already emits at the middle layer under OR (different bound parameter names, same filter). - Document the empty-predicate drop in buildQuery (safe under AND, narrowing under OR) and the defensive vacuously-true return in RepositoryUtils.checkKeyFilters. - Explain why validateEntityCountQuery uses the nullable getKeyFiltersOperation() rather than the OrDefault helper. - Add regression test asserting latest[ENTITY_FIELD] under OR only contains keys declared in entityFields.pull/15286/head
5 changed files with 46 additions and 3 deletions
Loading…
Reference in new issue