Structuring SQL database to accommodate models

I have the following models (simplified for demo):

public class Event
{
  public int Id { get; set;}
  public string Name { get; set;}
  public IEnumerable<Fight> Fights { get; set;}
}

public class Fight
{
  public int Id { get; set;}
  public int EventId { get; set;}
  // other unimportant properties
}

public class Event
{
  public int Id { get; set;}
  public string Name { get; set;}
  public IEnumerable<Fight> Fights { get; set;}
}

public class Fight
{
  public int Id { get; set;}
  public int EventId { get; set;}
  // other unimportant properties
}

I have set up two SQL tables:
- Events (columns: Id (PK), Name)
- Fights (columns: Id (PK), EventId(FK))

I have set the primary keys to be Identity in SQL, such that I leave the responsibility of creating the Ids to the database.

I read Event and Fight data from an external API. So when I have these objects in memory (after API call), the Ids for each of the objects are null (0). Currently, I have to write the Events to the database and return the objects that are written, so I can fetch the respective

EventId

EventId

properties to then use LINQ to assign to the relevant

Fight

Fight

model. Then I can write the

Fight

Fight

model to the database.

If I complete these database calls out of order (i.e. write

Fight

Fight

model to DB first), the DB write fails because the

Fight

Fight

model EventId isn't set. This feels to me like I've implemented a bad design approach, as this may not be obvious to other coders that the call order to the DB write is important (note this is only a personal project, so in reality it doesn't matter but I would like to understand a better approach).

I've tried to search this on google, but I'm finding it hard to reduce my situation into a query that gets valuable information.

Structuring SQL database to accommodate models

I have the following models (simplified for demo):

public class Event
{
  public int Id { get; set;}
  public string Name { get; set;}
  public IEnumerable<Fight> Fights { get; set;}
}

public class Fight
{
  public int Id { get; set;}
  public int EventId { get; set;}
  // other unimportant properties
}

public class Event
{
  public int Id { get; set;}
  public string Name { get; set;}
  public IEnumerable<Fight> Fights { get; set;}
}

public class Fight
{
  public int Id { get; set;}
  public int EventId { get; set;}
  // other unimportant properties
}

EventId

EventId

properties to then use LINQ to assign to the relevant

Fight

Fight

model. Then I can write the

Fight

Fight

model to the database.

If I complete these database calls out of order (i.e. write

Fight

Fight

model to DB first), the DB write fails because the

Fight

Fight

Structuring SQL database to accommodate models

Similar Threads

Structuring SQL database to accommodate models

Similar Threads

Similar Threads

Similar Threads