ModelBuilder: stackoverflow for may be invalid relationship via fluent api

[smitpatel]

Model

public class Blog
{
    public int Id { get; set; }
    public Blog MyBlog { get; set; }
    public Blog InverseBlog { get; set; }
}

// Write following in OnModelCreating method
modelBuilder.Entity<Blog>().HasOne(e => e.MyBlog).WithOne(e => e.InverseBlog).HasForeignKey<Blog>(e => e.Id);

Watch it 🔥

[smitpatel]

Throw in this line in OnModelCreating it ignores the relationship and creates database without FK.
modelBuilder.Entity<Blog>().Property(e => e.Id).HasColumnName("id");

[smitpatel]

This worked in 1.1.2 packages creating a self-ref fk. (defining such relationship is possible in SqlServer).
It initially gave error on cascade but setting behavior to restrict worked.

      CREATE TABLE [Blogs] (
          [Id] int NOT NULL,
          CONSTRAINT [PK_Blogs] PRIMARY KEY ([Id]),
          CONSTRAINT [FK_Blogs_Blogs_Id] FOREIGN KEY ([Id]) REFERENCES [Blogs] ([Id]) ON DELETE NO ACTION
      );

[AndriySvyryd]

Impact: Self-referencing PK-to-PK relationships cause stack overflow.
Risk: Low, the fix only affects this scenario