Skip to content

Releases: PawelGerr/Thinktecture.EntityFrameworkCore

7.1.0

30 Mar 10:59

Choose a tag to compare

  • Ctor-Overload for SqlServerBulkInsertOrUpdateOptions to specify whether HoldLock is desired or not.

7.0.0

08 Mar 17:22

Choose a tag to compare

  • [obsolete] Removing conventions is supported by EF 7 now
  • [SQL Server integration testing] The database must be locked during migrations and tear down.
  • SQLite doesn't need AddSchemaRespectingComponents by default
  • SqlServerTestDbContextProviderBuilder doesn't set the default schema "tests" by default anymore
  • Implemented SqliteTestDbContextProviderFactory that creates new providers which operate on a clone of previously migrated database.
  • Removed "BulkDelete" and "BulkDeleteAsync" because EF 7 supports this feature natively.
  • Added additional ITestIsolationOptions which uses DELETE FROM instead of TRUNCATE

4.5.1

14 Feb 21:09

Choose a tag to compare

  • Fixed member comparison

4.5.0

07 Feb 19:02

Choose a tag to compare

  • Added table hint for INDEX(name)

4.3.0

04 Dec 16:47

Choose a tag to compare

  • Testing: more flexibility for cleanup with ITestIsolationOptions
  • Fixed BulkUpdate/BulkInsertOrUpdate for entities with auto increment.

4.2.3

27 Apr 19:24

Choose a tag to compare

  • #20 Temp tables: use collation defined by model.

4.2.2

26 Apr 06:07

Choose a tag to compare

  • #22 Pre-sql server 2016 support for temp tables missed the DisposeAsync implementation.

4.2.1

25 Apr 17:19

Choose a tag to compare

  • #21 Fix pre-SQL Server 2016 compatibility of "drop table if exists" when disposing temp tables.

4.2.0

16 Feb 07:17

Choose a tag to compare

Features:

  • Automatic configuration of temp tables and collection parameters for primitive types can be disabled.
  • Temp tables and table hints: all limitations regarding SplittingBehavior and OwnedTypes are lifted.

Changes:

  • Collection parameters: by default, the collections is serialized immediately instead of deferred (configurable). This should be the expected behavior, because I can't image why I would create a parameter, then modify the underlying (in-memory-)collection and in the end execute the query expecting it has the last modifications. And there is a regression in 6.0.2 (dotnet/efcore#27427)

4.1.0

16 Feb 07:14

Choose a tag to compare

Features:

  • Added extension method for DbContextOptionsBuilder to remove conventions.
  • Added generic overload for ConfigureStringBuilderPool

Changes:

  • Moved IPrimaryKeyPropertiesProvider to their own files and moved the singletons to IPrimaryKeyPropertiesProvider for better IntelliSense support. PrimaryKeyPropertiesProviders is not obsolete.
  • Temp table for nullable primitive types are registered as well.
  • Convention registers scalar collection parameters for nullable structs as well
  • OpenJson should be strict to prevent buggy behavior