User475983607 posted
Hi all,
I simply get my data from context with the technique below
private readonly EvrakaContext _context;
public NumuneKabulController(EvrakaContext context)
{
_context = context;
}
public JsonResult NumuneSahibiBul(string ArananNumuneSahibi)
{
IQueryable<NumuneSahipleri> bulunanNumuneSahipleri = _context.NumuneSahipleri.Where(e => e.Adisoyadi.Contains(ArananNumuneSahibi)).Include(e => e.Evraklar).OrderByDescending(e => e.EvraklarId);
return Json(bulunanNumuneSahipleri);
}
however, as you see my context is not IDisposable and this make me concern about my server's RAM.
What do you think?
The construct shown in the snippet above is using constructor injection. I assume this is an ASP.NET Core application. The DbContext life time is determined by configuration set in ConfigurationServices. The default is "scoped" and which
looks similar to the following.
var connection = @"Server=SqlServer;Database=AdventureWorksLT2008R2;Trusted_Connection=True;";
services.AddDbContext<AdventureWorksLT2008R2Context>(options => options.UseSqlServer(connection));
Scoped services are scoped to the request. You get one DbContext for the duration of the a request.
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-2.2#service-lifetimes
Don't use "using" when implementing DI. In the case of a scoped service, you can either end up disposing the context prematurely or creating a new context where the entities are in different states.
