Skip to main content

Where clause

Mai mult ca sigur cu toții am folosit clauza where.
Pe scurt, where este folosit când trebuie sa adaugăm o constrângere la un tip generic specificat la o clasa sau la o metoda.
public class Car<TType>
where TType : ICarModel
{}
In exemplul de mai sus o sa putem folosii tipuri generice TType doar dacă implementează interfața ICarModel. In cazul in care vrem sa specificam ca tipul generic sa fie neaparat o clasa este nevoie sa ne folosim si de cuvantul rezervat class:
public class Car<TType>
where TType : ICarModel, class
{}
In cazul acesta, TType trebuie sa fie obligatoriu sa fie o clasa (nu va putea sa fie o structura de exemplu). Pentru structuri trebuie sa folosim cuvantul rezervat struct:
public class Car<TType>
where TType : struct
{}
Dar dacă vrem sa face new de un obiect de tip generic? In cazul aceasta trebuie sa specificam ca are un constructor default în clasau de where. Din păcate doar constructorul default fără parametri se poate specifica. In restul cazurilor o sa aveți nevoie de un factory sau de reflection pentru a crea noi instante din interiorul clasei Car.
public class Car<TType>
where TType : new()
{}
Gata cu introducerea, sa va zic ce vroiam de fapt. Cand avem 2 clause de where sintaxa este destul de ciudata, trebuie sa specificam de doua ori where.
public class Car<TType,TFormat>
where TType : new()
where TFormat : struct
{}
Mi se pare umpic mai ciudat ca cele doua where-uri nu sunt despartite prin virgula sau alt caracter (cuvînt rezervat).
Voua cum vi se pare sintaxa?

Comments

  1. Probabil ca sa simplifice un pic parser-ul: daca permiteau ceva de genul:
    where TType: IComparable, IEnumerable, TFormat : struct
    compiler-ul ar trebui sa se uite in avand ca sa isi dea seama ca TFormat nu e un tip de baza pentru TType, ci un tip generic..

    ReplyDelete
  2. Parserele pot fi mult mai inteligente decit sintem obisnuiti. Un exemplu bun este sintaxa Razor pentru ASP.Net MVC.

    In cazul asta, insa, cred ca "where" reprezinta cuvintul rezervat. Dupa definitia clasei poate fi o acolada deschisa, un punct si virgula sau un "where".

    ReplyDelete
  3. Dar dacă vreau sa specific încă o clasa de "where" nu mai este nevoie sa pun nici o virgula sau un alt caracter special. Mi s-a părut destul de interesant, pana ieri nici nu am observat lipsa acestui semn.

    ReplyDelete

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…