You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cross-tests with CodoMetis.ValueRanges on both lines: range and multirange columns as temporal-constraint periods and exclusion-constraint operands #42
Updated 2026-10-19 for the spin-off (#37): the two lines are EFCore.ComplexIndexes 5.x on release/5.x and SchemaKit 11.x on main.
The contract between the two libraries is the store type name. The PostgreSQL differ accepts a period whose store type ends in range, or whose CLR type is NpgsqlRange<T>. Every ValueRanges mapping carries that name (daterange, datemultirange, the custom timerange, …). Neither package references the other, and that stays so. The connection is proven by tests on both sides.
Here, with a test-only reference to the four ValueRanges packages:
On release/5.x, against ValueRanges 10.x:
HasTemporalConstraint(period: b => b.Period) over a DateRange, a RangeSet<DateRange, DateOnly> (multirange) and a TimeRange property passes validation, renders UNIQUE (… WITHOUT OVERLAPS), and the overlap is rejected on PostgreSQL 18.
HasExclusionConstraint with && over the same properties renders and rejects the overlap, on PostgreSQL 16 and 18.
A GiST HasComplexIndex over a range column serves a && query.
On main, against ValueRanges 11.0.0-preview.N:
the exclusion-constraint and GiST tests above, under the SchemaKit ids
ValueRanges carries the mirror tests: ComplexIndexesCrossTests and a joint smoke consumer on its 10 line, re-enabled against SchemaKit on its 11 line by CaffeinatedCoder/CodoMetis.ValueRanges#333.
changed the title [-]Cross-tests with CodoMetis.ValueRanges: its range and multirange columns as temporal-constraint periods and exclusion-constraint operands[/-][+]Cross-tests with CodoMetis.ValueRanges on both lines: range and multirange columns as temporal-constraint periods and exclusion-constraint operands[/+]on Oct 19, 2026
Activity
[-]Cross-tests with CodoMetis.ValueRanges: its range and multirange columns as temporal-constraint periods and exclusion-constraint operands[/-][+]Cross-tests with CodoMetis.ValueRanges on both lines: range and multirange columns as temporal-constraint periods and exclusion-constraint operands[/+]