Releases: linq2db/linq2db
Release 6.0.0 RC 1
Finally we have a new version of Linq To DB almost done.
Bases on amount and severity of reports for this release we will decide later wether we need another RC before final release.
For any questions regarding v6 migration, please use this discussion
Main changes in this (RC1) release:
- [breaking] we reorganized
Linq To DB
namespaces into two categories: general use public APIs inLinqToDB.*
and internal APIs (mostly intended for external provider development or advanced functionality) inLinqToDB.Internal.*
namespaces. If you cannot find some types/methods - check their new location in source or ask here - [breaking] async
IEnumerable
extensions were moved fromLinqToDB
namespace toLinqToDB.Async
to simplify resolve of naming conflicts for users who use other libraries with same extensions - [breaking] drop .NET 6 and EF.Core 6 support
- a lof of work were done to improve translation of predicates (especially complex) to SQL:
- complex predicate expressions that could fail translate before to SQL for all or for specific databases now should work
- a lot of new optimizations implemented to simplify predicates
- fixed support for mappings with
IsPredicate=true
option, done usingSql.FunctionAttribute
orSql.ExtensionAttribute
attributes - fixed a lot of issues in predicate generation, including fixes to nullability tracking for nested predicates
- multiple improvemens in JOINs generation:
- automatically promote
LEFT
joins toINNER
when query filters effectively already remove empty records - improve nullability tracking for
LEFT
joins
- automatically promote
- [all databases] fix/add translations of
string.PadLeft
,string.Length
andGuid.ToString()
members - add
Sql.Parameter(x)
andSql.Constant(x)
helpers to explicitly specify value translation type (as parameter or as literal) for specific value FromSqlScalar
API now expects user to usevalue
alias for column name. It will be generated automatically for databases, which support column aliases specification in subquery alias clause. For other databases it should be specified by user in SQL.- added
UseOptions
API on data context to temporary change context settings - added initial support for new SQL dialects: SQL Server 2025 and PostgreSQL 18
- [EF.Core] import enum mappings for PostgreSQL from EF.Core model
- [RemoteContext] released new remote context transports:
HttpClient
(server, client) andSignal/R
(server, client) - a lot of other bugfixes and improvements
For full list of changes check this page
New Contributors
- @denis-tsv made their first contribution in #4916
- @rameel made their first contribution in #4918
- @ffried made their first contribution in #4957
- @Akilaydin made their first contribution in #4970
- @GulpakMarina made their first contribution in #4868
Full Changelog: v6.0.0-preview.4...v6.0.0-rc.1
Release 6.0.0 Preview 4
Yet another preview release before upcoming release candidate.
Alongside with fixes to multiple bugs and regrssions from previous previews it contains following changes:
- Obsoletion of excess constructors on
DataConnection
andDataContext
types that could be replaced with constructor, acceptingDataOptions
configuration object - experimental support for new SQL Server
JSON
data type type - changes to default precision and scale mappings for decimal type from
DECIMAL
toDECIMAL(x, 10)
for many database providers. This mostly affects which data type is used byCreateTable
APIs by default - added
AllowMultiple=true
option to some mapping attributes, which didn't had it for some unknown reason - [SAP HANA] added support for
Sap.Data.Hana.Net.*
providers - fixed nuget generation issue for
linq2db.EntityFrameworkCore
packages, that resulted in incorrect package content for previous (Preview 3) release for EF 8 and 9
For full list of changes check this page
Full Changelog: v6.0.0-preview.3...v6.0.0-preview.4
Release 6.0.0 Preview 3
Small release to fix regression with interfaces, introduced in preview 2.
For full list of changes check this page
Full Changelog: v6.0.0-preview.2...v6.0.0-preview.3
Release 6.0.0 Preview 2
Release Highlights
Except more small changes, bugfixes and fixes to discovered regressions since preview 1 this release contains:
- various improvements to SQL predicates generation
- refactoring of T4 nugets
Select((entity, int index) => ...)
overload support with index parameter converted toROWNUMBER
window functionnet9.0
TFM supportlinq2db.EntityFrameworkCore
project was migrated to main repository to imrove its support and release it in sync with other projects
For full list of changes check this page
New Contributors
- @boginw made their first contribution in #4608
- @riktimmondal made their first contribution in #4635
- @johnjuuljensen made their first contribution in #4776
Full Changelog: v6.0.0-preview.1...v6.0.0-preview.2
Release 6.0.0 Preview 1
Release Highlights
This is a first preview of LINQ To DB 6 which includes completely rewritten query parser resulting in a lot of issues and limitations resolved. We recommend everyone to try it as we don't plan any other big changes before final release and your feedback will help us to polish it.
Note that we don't release LINQPad extension and EF.Core integration for first preview. They will be released with preview 2.
Also note that this release should fix more issues than currently marked as fixed in release notes as we didn't yet re-tested all repored issues. This will be done before next preview release.
New Contributors
- @tacosontitan made their first contribution in #4482
- @freakalis made their first contribution in #4493
Full Changelog: v5.4.1...v6.0.0-preview.1
Release 5.4.1
Release Highlights
- minor bugfix release
New Contributors
- @alexey-leonovich made their first contribution in #4443
- @AndreyShipunov made their first contribution in #4459
Full Changelog: v5.4.0...v5.4.1
Release 5.4.0
Release highlights:
- add library metrics collection API
- add support for one-way conversions in
MappingSchema
to specify logic for DB <-> application values conversion in one direction only - ensure library works with object <-> string conversions using
Invariant
culture everywhere - add support for
ClickHouse.Client
6.8.0+ provider versions - many small improvements and bug-fixes
Release 5.3.2
Release 5.3.1
Release 5.3.0
Release highlights
- implement fixes to avoid data context instance caching in query cache
- improvements to collection-typed parameter values logging
- fixed
null
support forvalue IN (subquery)
expressions - fixes several issues with
NativeAOT
builds - retract obsoletion note from T4 scaffold nugets
- many other fixes and improvements