Repository navigation
Document that range mappings resolve by store type name #56
Description
With the plugin active, the range mappings resolve by store type name: int4range resolves to Int32Range. Value sets deliberately don't do this, because text[] belongs to the provider's own string[] mapping.
It's harmless for scaffolding, but no document says so. A consumer who writes HasColumnType("int4range") on an NpgsqlRange<int> property, or reads the mapping by name, should know which CLR type answers.
Add it to docs/efcore.md, and decide whether the asymmetry with value sets is intended (it probably is). Found during the probing round (#52).
Activity
CaffeinatedCoder commentedon Oct 17, 2026
Moved off 9.1.0 into the backlog (#83), with no milestone.
release/9.xhas been cut, and 9.1.0 ships with the work that's already finished. Nothing has started on this issue, and it shouldn't hold up the tag. Docs, tests and internal work aren't tied to a version, so this doesn't need a milestone until someone picks it up.When someone picks it up, it goes under the epic of the release it will ship in and takes that milestone. A 9.x minor would need the change cherry-picked onto
release/9.x.