Provider-impacting changes


This page is no longer being updated. Changes that provider authors need to be aware of are marked with providers-beware.

This page contains links to pull requests made on the EF Core repo that may require authors of other database providers to react. The intention is to provide a starting point for authors of existing third-party database providers when updating their provider to a new version.

We are starting this log with changes from 2.1 to 2.2. Prior to 2.1 we used the providers-beware and providers-fyi labels on our issues and pull requests.

2.2 ---> 3.x

Note that many of the application-level breaking changes will also impact providers.

    • Removed obsolete APIs and collapsed optional parameter overloads
    • Removed DatabaseColumn.GetUnderlyingStoreType()
    • Removed obsolete APIs
    • Subclasses of CharTypeMapping may have been broken due to behavior changes required to fixing a couple bugs in the base implementation.
    • Added a base class for IDatabaseModelFactory and updated it to use a paramater object to mitigate future breaks.
    • Used parameter objects in MigrationsSqlGenerator to mitigate future breaks.
    • Explicit configuration of log levels required some changes to APIs that providers may be using. Specifically, if providers are using the logging infrastructure directly, then this change may break that use. Also, Providers that use the infrastructure (which will be public) going forward will need to derive from LoggingDefinitions or RelationalLoggingDefinitions. See the SQL Server and in-memory providers for examples.
    • Core, Relational, and Abstractions resource strings are now public.
    • CoreLoggerExtensions and RelationalLoggerExtensions are now public. Providers should use these APIs when logging events that are defined at the core or relational level. Do not access logging resources directly; these are still internal.
    • IRawSqlCommandBuilder has changed from a singleton service to a scoped service
    • IMigrationsSqlGenerator has changed from a singleton service to a scoped service
    • The infrastructure for building relational commands has been made public so it can be safely used by providers and refactored slightly.
    • ILazyLoader has changed from a scoped service to a transient service
    • IUpdateSqlGenerator has changed from a scoped service to a singleton service
    • Also, ISingletonUpdateSqlGenerator has been removed
    • A lot of internal code that was being used by providers has now been made public
    • It should no longer be necssary to reference IndentedStringBuilder since it has been factored out of the places that exposed it
    • Usages of NonCapturingLazyInitializer should be replaced with LazyInitializer from the BCL
    • This change is fully covered in the application breaking changes document. For providers, this may be more impacting because testing EF core can often result in hitting this issue, so test infrastructure has changed to make that less likely.
    • EntityMaterializerSource has been simplified
    • StartsWith translation has changed in a way that providers may want/need to react
    • Convention set services have changed. Providers should now inherit from either "ProviderConventionSet" or "RelationalConventionSet".
    • Customizations can be added through IConventionSetCustomizer services, but this is intended to be used by other extensions, not providers.
    • Conventions used at runtime should be resolved from IConventionSetBuilder.
    • Data seeding has been refactored into a public API to avoid the need to use internal types. This should only impact non-relational providers, since seeding is handled by the base relational class for all relational providers.

2.1 ---> 2.2

Test-only changes

Test and product code changes

  • - Consolidate RelationalTypeMapping.Clone methods
    • Changes in 2.1 to the RelationalTypeMapping allowed for a simplification in derived classes. We don't believe this was breaking to providers, but providers can take advantage of this change in their derived type mapping classes.
  • - Tagged or named queries
    • Adds infrastructure for tagging LINQ queries and having those tags show up as comments in the SQL. This may require providers to react in SQL generation.
  • - Support spatial data via NTS
    • Allows type mappings and member translators to be registered outside of the provider
      • Providers must call base.FindMapping() in their ITypeMappingSource implementation for it to work
    • Follow this pattern to add spatial support to your provider that is consistent across providers.
  • - Add enhanced debugging for service provider creation
    • Allows DbContextOptionsExtensions to implement a new interface that can help people understand why the internal service provider is being re-built
  • - Adds CanConnect API for use by health checks
    • This PR adds the concept of CanConnect which will be used by ASP.NET Core health checks to determine if the database is available. By default, the relational implementation just calls Exist, but providers can implement something different if necessary. Non-relational providers will need to implement the new API in order for the health check to be usable.
  • - Update base RelationalTypeMapping to not set DbParameter Size
    • Stop setting Size by default since it can cause truncation. Providers may need to add their own logic if Size needs to be set.
  • - RevEng: Always specify column type for decimal columns
    • Always configure column type for decimal columns in scaffolded code rather than configuring by convention.
    • Providers should not require any changes on their end.
  • - Adds CaseExpression for generating SQL CASE expressions
  • - Adds the ability to specify type mappings on SqlFunctionExpression to improve store type inference of arguments and results.