9.103.6.2

Download the library here

• EFCORE-VERSION CHANGES: With EF Core 9 released, the [efcore-version] in the [efcore-version].[major].[minor].[patch] versioning conventions will now be incremented from 8.x.y.z to 9.x.y.z.

Trial unlocked until the end of December

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.6.2

Download the library here

• ADDED: Support to key that use a NUMERIC type (Specific to PostgreSQL)
• UPDATED: Monthly Trial Release

Trial unlocked until the end of December

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.6.1

Download the library here

• UPDATED: Monthly Trial Release for EF6

Trial unlocked until the end of November

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.6.0

Download the library here

• ADDED: 2 news methods WhereExistsBulkInsert and WhereNotExistsBulkInsert. More documentation is coming in November. Meanwhile, you can reference this comment
• ADDED: Support to EF Core 9 RC2
• UPDATED: Monthly Trial Release

Trial unlocked until the end of November

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.5.0

Download the library here

• ADDED: Post "event" such as PostBulkSaveChanges, PostBulkInsert, etc.
• ADDED: Support to AutoTruncate feature to more provider (Specific to PostgreSQL)
• ADDED: New global option WhereBulkManager.ReplaceFirstTableNameOccurenceOnly that allow to replace only the first occurrence of the table for options such as WhereBulkContains (and other similar methods)
• FIXED: Issue when the generated alias had more than 63 characters (Specific to PostgreSQL)

Trial unlocked until the end of October

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.4.0

Download the library here

• ADDED: New option DisableAutoLoggingCommand. When adding a logging in EF Core, our library automatically log in it; This option will remove this behavior.
• ADDED: Support to ForceOutputFromUnmodifiedRow for BulkMerge (Specific to PostgreSQL)
• UPDATED: Monthly Trial Release

Trial unlocked until the end of October

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.3.0

Download the library here

• ADDED: UsePostgreSqlInsertOverridingSystemValue option to allow override system value during an insert statement (for BulkInsert, BulkMerge, BulkSynchronize, and BulkSaveChanges). See PostgreSQL Insert documentation for more detail.
• ADDED: UsePostgreSqlInsertOverridingUserValue option to allow override user value during an insert statement (for BulkInsert, BulkMerge, BulkSynchronize, and BulkSaveChanges). See PostgreSQL Insert documentation for more detail.
• ADDED: Logging now also log when a BinaryImport is used (Specific to PostgreSQL)
• FIXED: Issue with DeleteFromQuery when the table/view was using a schema name

Trial unlocked until the end of September

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.2.0

Download the library here

• ADDED: Support for Microsoft.Data.SqlClient for BatchSaveChanges (Specific to EF6)
• ADDED: New options PostgreSqlBinaryImportTimeout that will set the timeout when a BinaryImport is used (Specific to PostgreSQL)
• ADDED: Support to Time type (Specific to SQLite)
• FIXED: BulkInsertOptimized will no longer throw an error when passing an empty list
• UPDATED: Monthly Trial Release

Trial unlocked until the end of September

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.1.0

Download the library here

• ADDED: A new option for EF Core EntityType that could be useful when used with the IncludeGraphOperationBuilder.
• FIXED: Issue with InsertFromQuery for PostgreSQL when using a null-coalescing operator in the LINQ Expression (for EF6)
• UPDATED: Monthly Trial Release

Trial unlocked until the end of August

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions

8.103.0.0

Download the library here

• ADDED: Support to InsertStagingTableFilterFormula for PostgreSQL
• UPDATED: Monthly Trial Release

Breaking Change

The ForceValueGeneratedStrategy option has been replaced by the ExplicitValueResolutionMode option.

See the following code to understand how to replace the old options with the new options:

// The option `options.ForceValueGeneratedStrategy = ValueGeneratedStrategyType.OnAdd` has been replaced by:
options.ExplicitValueResolutionMode = Z.EntityFramework.Extensions.ExplicitValueResolutionMode.AlwaysKeepValueOnInsert;

// The option `options.ForceValueGeneratedStrategy = ValueGeneratedStrategyType.OnUpdate` has been replaced by
options.ExplicitValueResolutionMode = Z.EntityFramework.Extensions.ExplicitValueResolutionMode.AlwaysKeepValueOnUpdate;

// The option `options.ForceValueGeneratedStrategy = ValueGeneratedStrategyType.OnAddOrUpdate` has been replaced by:
options.ExplicitValueResolutionMode = Z.EntityFramework.Extensions.ExplicitValueResolutionMode.AlwaysKeepValueOnInsertOrUpdate;

You can find more about this breaking change in this article: How EFE Bulk Extensions handle explicit value in EF Core?

Trial unlocked until the end of July

NOTE: EF Extensions uses EFCore-Pinned Versionning conventions