Bdtjtk

I know that the default return here is the SQL Server database type, but I need the MySQL database type, the problem is to create a DbContext instance of the specified database type?

Of course, I know that it can also be created by specifying the connectionName, but the database connection string is encrypted and the string needs to be decrypted

The pseudo code is as follows:

public partial class MyDbContext : DbContext

{

    static string mysqlConn = ReadConnectionString(); //Get the encrypted MySQL connection string



    public MyDbContext() : base(mysqlConn)

    {

        // Even if I want to modify the connection string in this way, nor will it throw a connection string malformed exception

        Database.Connection.ConnectionString = DecryptConnectionString(mysqlConn);

    }

}

Ok, it's about what I expected, few of my questions can be answered.

Although I am not too familiar with EntityFramework, by looking at the source code of DbContext, I can almost certainly determine that this is a design flaw, it lacks a constructor like this:

Public DbContext(string connectionString, string providerName)

links below contais all essential snippets

Code based configuration EF6

MySql specific configuration EF6

To Serg Sh：
Thank you for taking the time to study this problem. I saw the solution you provided. By constructing the connection string, the final method is still:

Public DbContext(string nameOrConnectionString)

As I said before, this method returns the SQLServer database type. I insist that there is a problem with the DbContext design. Microsoft should delete this method and implement the following method groups:

//name of the connection string in the configuration file, Will automatically create a specific type of database connection based on the providerName of the configuration file

Public DbContext (string connectionName)





//connection string, the default returns SQLServer database type, namely: providerName = "System.Data.SqlClient"

Public DbContext (string connectionString)







//Connection string and data provider name

Public DbContext(string connectionString, string providerName)

If this is not the case, you can't escape the trap of the DbContext constructor.

In fact, I already have a plan that I don't want to use before asking this question:
Use a normal data connection string, feel free to fill in the parameters, read it and replace it with the actual string that has been decrypted and stored elsewhere.