Code First Migrations With Existing Table

Question

In my model I have navigation property Language:

public class IntegratorDescription : BaseContract
{
    [Key, Column(TypeName = "bigint"), DataMember]
    public long Id { get; set; }
    [DataMember, Column(TypeName = "bigint"), ForeignKey("Language")]
    public long LangId { get; set; }
    [DataMember]
    public string CompanyShortInfo { get; set; }
    [DataMember, Column(TypeName = "ntext")]
    public string CompanyInfo { get; set; }

    public virtual Models.Language Language { get; set; }
}

Language table already exists and it's done by another ORM, I need to say Migrations not to try to create Language table but update only Description table. How?

-"There is already an object named 'Languages' in the database."

Evgeniy · Accepted Answer · 2012-08-23 11:07:43Z

13

-IGNORECHANGES

Scaffolds an empty migration ignoring any pending changes detected in the current model. This can be used to create an initial, empty migration to enable Migrations for an existing database. N.B. Doing this assumes that the target database schema is compatible with the current model.

http://coding.abel.nu/2012/03/ef-migrations-command-reference/

answered Aug 23, 2012 at 11:07

Evgeniy

5551 gold badge7 silver badges26 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

BrainSlugs83 Over a year ago

Isn't there a way to have it create the table if it doesn't exist, and ignore the table if it does? This seems like a huge oversight in EF to me.

workabyte Over a year ago

i would hope ^ to be true but this post got me past my issue! TY

Collectives™ on Stack Overflow

Code First Migrations With Existing Table

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related