4

我已经使用Add-Migration. 当我Update-Database在空数据库上运行时，它会创建所有表，包括在 __MigrationHistory 表中添加一个条目。

现在我Update-Database再次运行只是为了测试，而不是“未检测到更改”我得到这个：

PM> Update-Database -Verbose -Project testProject.Web
Using StartUp project 'testProject.Web'.
Target database is: 'testProject_dbo' (DataSource: localhost, Provider: Devart.Data.MySql, Origin: Explicit).
Applying explicit migrations: [201203151243164_Start].
Applying explicit migration: 201203151243164_Start.
CREATE TABLE attachments ( 
 ...table data...
)
Table 'attachments' already exists
Table 'attachments' already exists

似乎更新不知道当前的数据库状态。唯一的解决方案是删除所有表并更新。如果我添加更多迁移，这也有效。

如您所见，我使用的数据库提供程序与平时不同（Devart.Data.Mysql），但我不确定问题是否存在。也许我错过了一些微不足道的东西？

4

2 回答 2

3

与DevArt沟通后问题得到解决。我从未IgnoreSchemaName在运行时生成的配置类中调用解决方法Enable-Migrations。总而言之，这是使它最终起作用的类：

internal sealed class Configuration : DbMigrationsConfiguration<YourDbContext>
{
    public Configuration()
    {
        // Because the Package Manager Console (NuGet) instantiates YourDbContext with the empty constructor,
        // a custom connection must be specified. Based on http://www.devart.com/blogs/dotconnect/?p=5603
        // Note that the MySqlProviderFactory must also be present in Web.config or App.config in the *startup project*
        // for this to work! Configuration example:

        /*
          <system.data>
            <DbProviderFactories>
              <clear />
              <remove invariant="Devart.Data.MySql" />
              <add name="dotConnect for MySQL" invariant="Devart.Data.MySql" description="Devart dotConnect for MySQL" type="Devart.Data.MySql.MySqlProviderFactory, Devart.Data.MySql, Version=6.30.196.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
            </DbProviderFactories>
          </system.data>
        */

        // Apply the IgnoreSchemaName workaround
        MySqlEntityProviderConfig.Instance.Workarounds.IgnoreSchemaName = true;

        // Create a custom connection to specify the database and set a SQL generator for MySql.
        var connectionInfo = MySqlConnectionInfo.CreateConnection("<Your ConnectionString>");

        TargetDatabase = connectionInfo;
        SetSqlGenerator(connectionInfo.GetInvariantName(), new MySqlEntityMigrationSqlGenerator());

        // Enable automatic migrations if you like
        AutomaticMigrationsEnabled = false;

        // There is some problem with referencing EntityFramework 4.3.1.0 for me, so another fix that needs
        // to be applied in Web.config is this:

        /*
          <runtime>
            <assemblyBinding>
              <!-- This redirection is needed for EntityFramework Migrations through the Package Manager Console (NuGet) -->
              <dependentAssembly>
                <assemblyIdentity name="EntityFramework" publicKeyToken="b77a5c561934e089" />
                <bindingRedirect oldVersion="4.3.0.0" newVersion="4.3.1.0" />
              </dependentAssembly>
            </assemblyBinding>
          </runtime>
        */

        // After these Web.config additions, running migrations in Package Manager Console should be as easy as:
        // Update-Database -Verbose -ProjectName Your.MigrationsProject

        // Creating new migrations:
        // Add-Migration -Name MigrationDescription -ProjectName Your.MigrationsProject
    }
}

之后我再次清空数据库以生成正确的迁移历史条目，一切都很好。DevArt提供了有关配置的更多详细信息。

于 2012-03-16T15:19:18.383 回答
1

我有同样奇怪的行为，但在我的情况下，它变得更简单：代码合并将我的启动项目重置为默认值，这不是包含迁移的项目。

直到我尝试了这个标志，我才注意到-Verbose，它明确指出我的启动项目与包管理器中配置的 NuGet 项目不同。

值得仔细检查！

于 2014-03-17T20:47:40.410 回答