- Alter the paths of the individual Get, Put, and Delete endpoints to contain two (or more, depending on how many keys are in your composite) parameters, and then alter the method parameters to match. This requires careful consideration as there are many different ways you can structure the parameters in your route.
- Alter every usage of _context.nameOfModelHere.FindAsync to contain all components of your primary key. Look at the model’s Entity definition in your database context class, specifically the usage of entity.HasKey, to determine the order in which to list the components in your key to FindAsync.
- Alter the nameOfModelHereExists method to take the correct amount of parameters for your key. Adjust the body of the method accordingly to check all parts of the key; I just added && at the end of the existing equality expression, and added more equality expressions.
- Alter all usages of nameOfModelHereExists appropriately.
- In the Put method, alter the second if statement to check all the components of your primary key, rather than just id.
- In the Post method, adjust the CreatedAtAction call in the return statement to contain all the components of your primary key.
- I would also recommend updating all the auto-generated comments that EntityFramework put in to keep things consistent.
Sunday, 31 March 2019
Dealing with composite primary keys and EntityFramework scaffolded controllers
A recent uni assignment has required me to implement an ASP.NET Core REST API using EntityFrameworkCore on a pre-existing database. Whilst EF Core tends to generate controllers for models with single primary keys just fine, I’ve found that it has no support for composite primary keys. This requires you to alter your controller classes to add the support manually, which in my case involved the following;