Apply naming conventions to sequences

[roji]

[roji]

This actually makes no sense. The only way to define a sequence is to specify it using the fluent API, where you already have to specify the name (and override any convention, provided by the plugin or otherwise).

[mjuen]

This assumption does not seem to hold when using UseTpcMappingStrategy.

Here a minimal example concerning the issue:

public class DemoContext : DbContext
{
   protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
   {
       optionsBuilder
           .UseNpgsql("")
           .UseSnakeCaseNamingConvention();
   }

   protected override void OnModelCreating(ModelBuilder modelBuilder)
   {
       modelBuilder.Entity<Invoice>().UseTpcMappingStrategy();
   }

   public DbSet<CustomerInvoice> CustomerInvoices { get; set; }

   public DbSet<SupplierInvoice> SupplierInvoices { get; set; }

   public abstract class Invoice
   {
       public long Id { get; set; }
   }

   public class CustomerInvoice : Invoice
   {
       public long CustomerId { get; set; }
   }

   public class SupplierInvoice : Invoice
   {
       public long SupplierId { get; set; }
   }
}

When creating a migration a sequence with the name InvoiceSequence is produced.

[roji]

You're right, this is a new thing in 7.0. I'll try to take a look at this soon - in the meantime, explicitly specify the sequence name as a workaround.