Skip to main content

Definirea unui mecanism de comparare a entitatiilor din punct de vedere a structurii folosind IStructuralEquatable

Uneori avem nevoie sa putem compara clasele de tip POCO ca pe niste structuri. De exemplu daca avem clasa Student, dorim sa comparam entitatile de acest tip din punct de vedere a datelor pe care le contin.
class Student
{
public string Nume{ get;set;}
public string Prenume{ get;set;}
public int Varsta{ get;set;}
}
Pentru acest lucru sa folosim IStructuralEquatable. Aceasta interfata a fost creata pentru a fi folosita in tupluri. In cazul acestora, doua tupluri sunt egale daca fiecare element din tuplu este egal din celalalt tuplu.
Interfata contine doua metode:
bool Equals(Object other, IEqualityComparer comparer);
int GetHashCode(IEqualityComparer comparer);
Prin intermediul parametrului comparer se defineste mecanismul de comparare. Exista cateva implementari in .NET pentru IEqualityComparer prin care putem sa comparam siruriile de elemente - element cu element.
Valoarea default a acestui parametru este EqualityComparer>Object<.Default.Equals in cazul in care se foloseste mecanismul standard de comparare. O alta implementare este StructuralComparisons.StructuralEqualityComparer. Aceasta este folosita cand lucram cu tupluri sau cu clase ce implementeaza IStructuralEquatable.
Dar ne putem defini si noi propriul mecanism de comparare daca implementam IEqualityComparer. De exemplu in cazul nostru am putea sa avem:
public class FullNameComparer
{
public new bool Equals(object s1, object s2)
{
...
var student1 = s1 as Student;
var student2 = s2 as Student;
return student1.Nume == student2.Nume && student1.Prenume == student2.Prenume;
}
}
Pentru a putea compara doi studenti putem sa apelam( clasa Student trebuie sa implementeze IStructuralEquatable):

var student1 = new Student() { ... };
var student2 = new Student() { ... };
bool areEquals = student1.Equals(student2, new FullNameComparer());
Unde ne este utiliza aceasta interfata. Cand avem nevoie sa definim mai multe mecanism de comparare pentru o clasa de un anumit fel. Prin acest mecanism putem foarte usor sa trimitem printr-un parametru modul in care sa se faca compararea. Cel mai bine aceasta interfata se preteaza cand lucram cu tupluri.
Exista nenumarate solutii la aceasta problema, depinde de la caz.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too