Repository navigation
SqlLinqer 2.4.0-rc.2
Pre-releaseSqlLinqer 2.4.0-rc.2 replaces JSON result transport with native database values for typed queries. This candidate is intended for application validation before a stable release.
Changes
- Stream complete parent models with their selected nested data. Server providers use correlated native records; SQLite uses prepared child queries on the same connection.
- Keep filtering, DISTINCT, grouping, ordering, and paging in SQL. Parent DISTINCT compares selected scalar columns and required relationship keys. It does not deduplicate child collections or compare object graphs in memory.
- Support SQLite nested DISTINCT with
PRAGMA query_only=ON, without library-created TEMP tables. - Share constructor/member mapping between native and tabular readers. Reduce temporary allocations and use shorter compilation-scoped aliases.
- Preserve cancellation, early stream termination, and caller-owned connection/transaction handling.
- Remove the core System.Text.Json dependency. The .NET Standard 2.1 asset has no package dependencies; 2.0 retains Microsoft.Bcl.AsyncInterfaces for async compatibility.
Compatibility
The supported typed query interfaces remain the compatibility target. JSON-specific APIs, low-level connector functions, and string-only rendering extensions are not preserved. Typed SELECT rendering extensions use CompileSelect and must preserve the compiled result layout.
For .Select(Name).Select(Permissions).Distinct(), different relationship IDs keep same-name users separate. Child rows retain their SQL multiplicity. With DISTINCT, order by a selected scalar column or required relationship key.
Validation limits
Live Azure SQL and Windows .NET Framework runtime testing have not been performed locally. The core continues to target .NET Standard 2.0 and 2.1. Please validate your application's models, queries, cancellation, and transactions against this prerelease before deployment.