代码优先迁移中的二进制字段

Question

Regards,

I have problems with migrations and binary fields...

My initial migration looks like this (I had an existing database):

public override void Up()
{
    CreateTable("dbo.Words", c => new
    {
        ID = c.Int(nullable: false, identity: true),
        Name = c.String(maxLength: 4000),
        Image = c.Binary(),
        Audio = c.Binary(),
    }).PrimaryKey(t => t.ID);
}

And the Entity class is here:

public class Word
{
    public int ID { get; set; }
    public string Name { get; set; }
    [MaxLength]
    public byte[] Image { get; set; }
    [MaxLength]
    public byte[] Audio { get; set; }
}

I have automatic migrations turned on. Now if I drop all the tables from the database and run "Update-Database" I get:

Applying code-based migration: 201304211813502_InitialMigration.
Applying automatic migration: 201304212024538_AutomaticMigration.
System.Data.SqlServerCe.SqlCeException (0x80004005): Cannot alter column of type NTEXT or IMAGE [ Column Name = Image ]

So it looks like something is not in sync.. I run "Add-Migration AutoMigration" to see what entity framework had in mind it has to still be updated... The file I get is here:

public partial class AutoMigration: DbMigration
{
    public override void Up()
    {
        AlterColumn("dbo.Words", "Image", c => c.Binary());
        AlterColumn("dbo.Words", "Audio", c => c.Binary());
    }

    public override void Down()
    {
        AlterColumn("dbo.Words", "Audio", c => c.Binary(maxLength: 4000));
        AlterColumn("dbo.Words", "Image", c => c.Binary(maxLength: 4000));
    }
}

So... from this it looks like EF thinks Image and Audio fields are Binary(maxLength: 4000).. but they're not supposed to be!! (because in the initial migration they are Binary() ).

So I'm stuck and cannot get up-to-date with my migrations... and I need MaxLength (unlimited) binary fields...

What could be going on here? thank you! david

Answer 1

I finally managed to upgrade the project to EF 6.0.0 Alpha3 ... I had to fix a lot of small problems and also upgrade NuGet to 2.5 RC. Now it works.. not sure what I did but most likely it was just an upgrade to EF 6