Getting an error while “update-database” command is running: There is already an object named '…' in...
up vote
2
down vote
favorite
I have a few EF Core models:
abstract class Weapon {
public int Id { get; set; }
public string Name { get; set; }
}
class Axe : Weapon {
}
class Sword : Weapon {
}
class GameDbContext : DbContext {
public DbSet<Weapon> Weapons { get; set; }
public GameDbContext(DbContextOptions options) : base(options){
this.Database.EnsureCreated();
}
protected override void OnModelCreating(ModelBuilder modelBuilder) {
base.OnModelCreating(modelBuilder);
this.SetModelsConfigurations(modelBuilder);
modelBuilder.Entity<Axe> ().HasBaseType<Weapon>();
modelBuilder.Entity<Sword>().HasBaseType<Weapon>();
}
}
When I run "add-migration" command everything is Ok. But when I run "update-database" command, I get an error:
There is already an object named 'Weapons' in the database.
This DB wasn't created. Why do I get this error? Please explain to me how DB models should be configured.
c# asp.net entity-framework ef-core-2.1
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
add a comment |
up vote
2
down vote
favorite
I have a few EF Core models:
abstract class Weapon {
public int Id { get; set; }
public string Name { get; set; }
}
class Axe : Weapon {
}
class Sword : Weapon {
}
class GameDbContext : DbContext {
public DbSet<Weapon> Weapons { get; set; }
public GameDbContext(DbContextOptions options) : base(options){
this.Database.EnsureCreated();
}
protected override void OnModelCreating(ModelBuilder modelBuilder) {
base.OnModelCreating(modelBuilder);
this.SetModelsConfigurations(modelBuilder);
modelBuilder.Entity<Axe> ().HasBaseType<Weapon>();
modelBuilder.Entity<Sword>().HasBaseType<Weapon>();
}
}
When I run "add-migration" command everything is Ok. But when I run "update-database" command, I get an error:
There is already an object named 'Weapons' in the database.
This DB wasn't created. Why do I get this error? Please explain to me how DB models should be configured.
c# asp.net entity-framework ef-core-2.1
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
1
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have a few EF Core models:
abstract class Weapon {
public int Id { get; set; }
public string Name { get; set; }
}
class Axe : Weapon {
}
class Sword : Weapon {
}
class GameDbContext : DbContext {
public DbSet<Weapon> Weapons { get; set; }
public GameDbContext(DbContextOptions options) : base(options){
this.Database.EnsureCreated();
}
protected override void OnModelCreating(ModelBuilder modelBuilder) {
base.OnModelCreating(modelBuilder);
this.SetModelsConfigurations(modelBuilder);
modelBuilder.Entity<Axe> ().HasBaseType<Weapon>();
modelBuilder.Entity<Sword>().HasBaseType<Weapon>();
}
}
When I run "add-migration" command everything is Ok. But when I run "update-database" command, I get an error:
There is already an object named 'Weapons' in the database.
This DB wasn't created. Why do I get this error? Please explain to me how DB models should be configured.
c# asp.net entity-framework ef-core-2.1
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
I have a few EF Core models:
abstract class Weapon {
public int Id { get; set; }
public string Name { get; set; }
}
class Axe : Weapon {
}
class Sword : Weapon {
}
class GameDbContext : DbContext {
public DbSet<Weapon> Weapons { get; set; }
public GameDbContext(DbContextOptions options) : base(options){
this.Database.EnsureCreated();
}
protected override void OnModelCreating(ModelBuilder modelBuilder) {
base.OnModelCreating(modelBuilder);
this.SetModelsConfigurations(modelBuilder);
modelBuilder.Entity<Axe> ().HasBaseType<Weapon>();
modelBuilder.Entity<Sword>().HasBaseType<Weapon>();
}
}
When I run "add-migration" command everything is Ok. But when I run "update-database" command, I get an error:
There is already an object named 'Weapons' in the database.
This DB wasn't created. Why do I get this error? Please explain to me how DB models should be configured.
c# asp.net entity-framework ef-core-2.1
c# asp.net entity-framework ef-core-2.1
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
asked Nov 19 at 16:57
Evgeniy Miroshnichenko
416617
416617
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
1
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18
add a comment |
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
1
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
1
1
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379376%2fgetting-an-error-while-update-database-command-is-running-there-is-already-an%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Only use Migrate or MigrateAsync. This will already create a database. The CreateDatabase command itself will create a database according to it's current model, disregarding your migration logic.
– Silvermind
Nov 19 at 16:59
@Silvermind Is that a command? Or Method?
– Evgeniy Miroshnichenko
Nov 19 at 17:02
1
@Silvermind ( I see that problem was with method: this.Database.EnsureCreated(). "update-databes" command was done after this method was deleted.
– Evgeniy Miroshnichenko
Nov 19 at 17:16
I'm sorry. I thought you were using migrations in code. If you're using the cli, you should just be able to use update-database according to the docs
– Silvermind
Nov 19 at 17:16
Ah, thats why I mixed them up. Yeah I meant EnsureCreated instead of CreateDatabase. Don't use that command with migrations. ;)
– Silvermind
Nov 19 at 17:18