Skip to main content

Entity Framework: How to get in a generic way entities from EF based on entity IDs

Offtopic:
I’m back. After a few weeks when I was blocked with personal projects, I’m back on the field, ready to write technical content.
Today I’ll start with something lights that can make our day more beautiful.

How we can write a generic method to get an entity from database using Entity Framework?
Let’s assume that we have different types of entities and we would like to obtain a specific entity using a generic method. Each entity can have the primary key field called in different ways. Also the type of the field can be different (one can be string, another one int and so on).
For this cases we should use Find method. This method accept as input parameters a collections of objects that represents the keys of the entity. Using this method we can get entities from EF in a generic way.
For compound keys, you need to specify the keys in the same order you specified them when you mapped the entity in EF.
Why a list of keys and not only one input parameter?
Well, we can have entities that has a compound key (a key formed from more than one field). For this cases we need to be able to specify the list of keys.
How to get a DbSet based on entity type?
When we need to get a specific DbSet based on the entity type we can use the Set method of DbContext. This methods returns the DbSet for specific entity.

Code sample:
FooDbContext fooContext = new FooDbContext();
// Get DbSet from DbContext
DbSet<Foo> fooSet = fooContext.Set<Foo>();

// Foo with id=2
Foo foo = fooSet.Find(2);

// Get entity with a compound key where key is ("BMW","M3")
DbSet<Car> carSet = fooContext.Set<Car>();
Car bmwM3 = carSet.Find("BMW",M3");

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...