Because We Need to Talk About Kevin.
Generates table with chosen column names of the right type in the given order.
Generates table with chosen column names of the right type (look at date :O) in the given order.
Given:
public class Thing
{
public int Id { get; set; }
[Range(0, 10)] // <= We are checking this
public int SecondInt { get; set; }
}Given:
public class Thing
{
public int Id { get; set; }
[Range(0, 10)] // <= We are checking this
public int SecondInt { get; set; }
}[Range(0,10)] gets ignored : [SecondInt] int NOT NULL.
Same behaviour as Sql Server: "SecondInt" INTEGER NOT NULL.
has entity with a default index
has entity with combined sorted index
Generates TEXT.
looking what schema does for Generic Identity without mapping
looking what schema does for Generic Identity without mapping
looking what schema does for Generic Identity with mapping
has entity with a default index
has entity with combined sorted index
Generates required properties that will be created even if they are null or empty.
Generates required properties that will be created even if they are null or empty.
NullThing Generates NULL.
SomeThing Generates NOT NULL.
SomeThingId adds ON DELETE CASCADE to the foreign key definition
NullThing does not add ON DELETE CASCADE to the foreign key definition
NullThing Generates NULL.
SomeThing Generates NOT NULL.
SomeThingId adds ON DELETE CASCADE to the foreign key definition
NullThing does not add ON DELETE CASCADE to the foreign key definition
int Generates int NOT NULL.
int? Generates int NULL.
int Generates INTEGER NOT NULL.
int? Generates INTEGER NULL
string Generates NOT NULL.
string? Generates NULL.
string Generates NOT NULL.
string? Generates NULL.
Because the entity used in the DbSet has a collection of another entity type, the latter are mapped as well.
EF infers and includes related entities in bidirectional relationship in the schema even when only one side is explicitly registered in the DbContext.
EF infers and includes related entities in bidirectional relationship in the schema even when only one side is explicitly registered in the DbContext, but reversed this time. CREATE TABLE switches to different DBSets to create tables from.
Same behavior as SqlServer with bidirectional relationship, relationship discovery pulls in the Blog entity despite only registering Post
Because the entity used in the DbSet has a collection of another entity type, the latter are mapped as well.
EF infers and includes related entities in the schema even when only one side is explicitly registered in the DbContext.
Same behavior as SqlServer, relationship discovery pulls in the Blog entity despite only registering Post