Doka.EntityFrameworkCore.NestedSet.SqlServer 10.2.0

Doka.EntityFrameworkCore.NestedSet.SqlServer

Native SQL Server integration for the shared NestedSet EF hierarchy engine. This adapter owns native SQL, model/index conventions, registry transport, and query translation while the common package owns hierarchy algorithms and transaction/lifecycle coordination.

Install

dotnet package add Doka.EntityFrameworkCore.NestedSet.SqlServer --version 10.2.0

The adapter brings in Doka.EntityFrameworkCore.NestedSet, Doka.NestedSet, and Microsoft.EntityFrameworkCore.SqlServer [10.0.13,11.0.0) transitively. Use one qualified NestedSet version across the application's NestedSet packages. Version 10.2.0 is the stable six-package contract.

The adapter requires exactly the matching common EF kernel version, [10.2.0] for this release. Update all selected NestedSet adapters together.

This release adds common HasTreeRegistryTable(...) configuration and corrects manual-detection/save-recovery behavior. Registration remains in the native provider callback; the default registry schema is unchanged.

The shipping dependency graph explicitly raises System.Security.Cryptography.Pkcs to a minimum of 9.0.21, without an upper bound, for the native SQL Client path. That security floor is a SQL Server adapter dependency, not a dependency of the common kernel. Repository qualification uses PKCS 10.0.14 for .NET 10; applications already using the patched 9.0.21 need no forced update. Native SQL Server qualification requires supported Linux x86-64 hosts; ARM emulation is not the supported qualification environment.

Register

Call UseNestedSets() inside the native provider callback:

using Microsoft.EntityFrameworkCore;
using Doka.EntityFrameworkCore.NestedSet;

services.AddDbContext<ApplicationDbContext>(options => options
    .UseSqlServer(connectionString, sqlServer => sqlServer.UseNestedSets()));

Keep entity configuration through HasNestedSet(...), queries/mutations through context.NestedSet<TEntity>(), and existing application save/transaction rules. No additional hierarchy entity or provider-specific domain model is required. Ordinary EF migrations are the baseline; SafeMigrations is independently optional.

The former options-level DbContextOptionsBuilder.UseNestedSets() overloads are removed. See the upgrade guide, configuration, and support/qualification matrix.

Composition query plans

Public composition operations, such as SelectAncestors(...), SelectSubtrees(...) and WherePathEdges(...), tag their queries with Doka.EntityFrameworkCore.NestedSet composition. The adapter appends OPTION (OPTIMIZE FOR UNKNOWN, MAXDOP 1) to commands carrying that tag only. SQL Server otherwise reuses a plan compiled for the first selection size and can repeat population-sized work for later sources or parallel workers. Ordinary hierarchy reads, mutations and untagged application queries are unchanged. Do not append a second OPTION clause to tagged commands; see SQL Server composition plans.