Fixes #20497: Add range_contains lookup and fix VLANGroup VID range filtering
#20514
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.
Fixes: #20497
Summary
Introduce a generic ORM lookup
range_containsforArrayField(RangeField)to correctly match rows where a scalar value is contained by any range in the array (e.g.,VLANGroup.vid_ranges). This replaces the raw‑SQL helper used by the VLAN group filter and aligns REST and GraphQL semantics with PostgreSQL range operators.Changes
range_containslookup (guarded toArrayField(RangeField)).VLANGroupFilterSet (contains_vid) to use the lookup (remove raw SQL).IntegerRangeArrayLookupinput and wireVLANGroup.vid_rangesto it.vid_ranges: { contains: <Int> }, which maps internally to__range_contains.Tests
?contains_vid=<int>(hit/miss and exclusive upper bound).