Repository navigation
Test JSON-column readers and writers through a compiled model #43
Description
The JSON-column readers and writers point ConstructorExpression at their static Instance so compiled models can use them. During the 9.0.0 review this was checked once by hand with dotnet ef dbcontext optimize, and nothing guards it now.
Add a test that generates a compiled model for a context with range and value set properties inside a JSON column, and round-trips a row through it against a live server.
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.CaffeinatedCoder commentedon Oct 18, 2026
Pre-tag analysis (#179, part B):
CompiledModelJsonTestspasses withLiteralJsonValueReaderWriter.ConstructorExpression => throw new NotSupportedException()seeded, because the standard compiled model never consultsConstructorExpression(commit a00e7bf says so too). The test holds the JSON round trip through a standard compiled model, which is worth keeping, but not theConstructorExpressionpath this issue named. That path is exercised only by the Native AOT compiled model, so the obligation moves to #209 (backlog): its test must fail with that seed.