Automatically determine the database provider and handle on module mapping code

[hikalkan]

In some cases, module extension methods (example) needs to know the actual database provider being used.

Until now, we provided an option on the extension method call:

builder.ConfigureIdentityServer(options =>
{
	options.DatabaseProvider = EfCoreDatabaseProvider.MySql;
});    

No need to this anymore. ABP Framework automatically determines the provider and sets it on the modelbuilder

abp/framework/src/Volo.Abp.EntityFrameworkCore/Volo/Abp/EntityFrameworkCore/AbpDbContext.cs

Lines 113 to 145 in 6d7b49d

	protected virtual void TrySetDatabaseProvider(ModelBuilder modelBuilder)
	{
	var provider = GetDatabaseProviderOrNull(modelBuilder);
	if (provider != null)
	{
	modelBuilder.SetDatabaseProvider(provider.Value);
	}
	}
	protected virtual EfCoreDatabaseProvider? GetDatabaseProviderOrNull(ModelBuilder modelBuilder)
	{
	switch (Database.ProviderName)
	{
	case "Microsoft.EntityFrameworkCore.SqlServer":
	return EfCoreDatabaseProvider.SqlServer;
	case "Npgsql.EntityFrameworkCore.PostgreSQL":
	return EfCoreDatabaseProvider.PostgreSql;
	case "Pomelo.EntityFrameworkCore.MySql":
	return EfCoreDatabaseProvider.MySql;
	case "Devart.Data.Oracle.EFCore":
	return EfCoreDatabaseProvider.Oracle;
	case "Microsoft.EntityFrameworkCore.Sqlite":
	return EfCoreDatabaseProvider.Sqlite;
	case "Microsoft.EntityFrameworkCore.InMemory":
	return EfCoreDatabaseProvider.InMemory;
	case "FirebirdSql.EntityFrameworkCore.Firebird":
	return EfCoreDatabaseProvider.Firebird;
	case "Microsoft.EntityFrameworkCore.Cosmos":
	return EfCoreDatabaseProvider.Cosmos;
	default:
	return null;
	}
	}

Module extension methods can get it like modelBuilder.IsUsingMySQL()

If it can't determine automatically, you can still call it like modelBuilder.UseMySql(); in the OnModelCreating of your DbContext that overrides it.

So, no need to set it for every module. I marked the DatabaseProvider option of the ConfigureIdentityServer as obsolete.