Skip to main content

Dictionary - custom key type

In ultimele 2 saptamani am luat la puricat .NET Collections si m-am gandit ca merita sa vorbim astazi putin despre cheile unui dictionar( Dictionary) - map.
In general lucram cu chei care sunt de tip value type.

Dictionary<int, Door> map = new Dictionary<int, Door>();
map.Add(1,door1);
map.Add(2,door2);
...
var door1 = map[1];
In acest caz, cheia o sa fie gasita fara nici o problema. Dar ce se intampla cand cheia noastra este reprezentata de un tip declarat de noi?
Dictionary<DoorKey,Door> map = new Dictionary<DoorKey, Door>();
map.Add(doorKey1, door1);
map.Add(doorKey2, door2);
....
var door1 = map[copyOfDoorKey1];
In momentul cand o sa dorim sa facem retrive la element pe baza de cheie, o sa observam ca elementul nu este gasit( o eroare de tip KeyNotFoundException o sa fie aruncata). In debug daca ne uitam la ce elemente contine dictionarul, o sa observam ca avem doua elemente cu cheiule pe care le-am astepta, dar totusi nu putem sa facem retrive la date.
Fiecare colectie de tip (cheie,valoare) are implementari diferete, dar in general una sau mai multe elemente sunt grupate intr-un bucket( galeata), pe baza la hash code. Dimensiunea sau distributia pe valori a acestuia difera, dar ce trebuie sa retinem aici este ca fiecare element este adaugat intr-un anumit bucket pe baza unui hash returnat de catre cheie. Dupa ce este identificat bucket-ul, se face o cautare a cheii in bucket-ul respectiv pe baza metodei Equal.
Indiferent de metoda de implementare a dictionarului, cautarea se face pe baza acestor doua metode. Din acesta cauza, in exemplul dat mai sus o sa ne trezim ca elementul nu este gasit niciodata, chiar daca teoretic in colectie avem cheie data.
Pentru toate tipurile de date pe care o sa le folosim pe post de cheie, este nevoie sa facem override la GetHashCode si Equal. Mai jos putem sa gasim un exemplu pentru clasa DoorKey
class Doorkey
{
    int RoomNumber { get; set; }
    int DoorNumber {get; set; }
    public override bool Equals(object obj)
    {
        if( obj == null
            || !( obj is DoorKey ))
        {
            return false
        }
        return RoomNumber == obj.RoomNumber
            && DoorNumber == obj.DoorNumber
    }
    public override int GetHashCode()
{
    return RoomNumber.GetHashCode();
}
}
Pentru metoda GetGashCode, aceasta nu este cea mai buna implementara. Cea mai importanta regula pe care metoda GetHashCode trebuie sa o respecte este ca valoarea returnata sa fie aceiasi pentru un obiect care are aceiasi stare( valoare).
Asa ca, de fiecare data cand lucram cu dictionarele( maps) din .NET, iar cheile sunt reprezentate de tipuri custom, nu trebuie sa uitam sa facem ovveride la GetHashCode si Equals, in caz contrat o sa ne trezim ca nu putem sa obtinem datele pe baza cheii.

Comments

Post a Comment

Popular posts from this blog

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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…