Entity Framework Core 2.1 problem with DetachedLazyLoadingWarning









up vote
1
down vote

favorite
1












I get an exception with DetachedLazyLoadingWarning:




Error generated for warning 'Microsoft.EntityFrameworkCore.Infrastructure.DetachedLazyLoadingWarning: An attempt was made to lazy-load navigation property 'Product' on detached entity of type 'DeliveryProxy'. Lazy-loading is not supported for detached entities or entities that are loaded with 'AsNoTracking()'.'. This exception can be suppressed or logged by passing event ID 'CoreEventId.DetachedLazyLoadingWarning' to the 'ConfigureWarnings' method in 'DbContext.OnConfiguring' or 'AddDbContext'.




while trying to query SQL database with Entity Framework Code 2.1



This is my query:



var orders = 
_context
.Set<Order>()
.Where(v => v.CompanyId == companyId)
.Include(v => v.Details)
.ThenInclude(d => d.Delivery)
.ThenInclude(v => v.Product)
.OrderByDescending(v=> v.Details.FirstOrDefault().Delivery.Product.ProductId)
.ThenByDescending(v=> v.Details.FirstOrDefault().Delivery.Value)
.ThenByDescending(v => v.CreatedAt)
.Page(request.Page, request.RowsPerPage);


Here are entities and relationships:



public class Order : IEntity<int>

public int CompanyId get; set;

public virtual ICollection<OrderDetails> Details get; set;

[Required]
public DateTimeOffset CreatedAt get; set;

[Key]
public int Id get; set;


public class OrderDetails : IEntity<int>

public int OrderId get; set;

public int DeliveryId get; set;

[ForeignKey(nameof(OrderId))]
public virtual Order Order get; set;

[ForeignKey(nameof(DeliveryId))]
public virtual Delivery Delivery get; set;

[Key]
public int Id get; set;


public class Delivery : IEntity<int>

[Required]
public int ProductId get; set;

public int Value get; set;

[ForeignKey(nameof(ProductId))]
public virtual Product Product get; set;

[Key]
public int Id get; set;


[Table("Products")]
public class Product : IEntity<int>

[Required]
public byte ProductCategoryId get; set;


public virtual ICollection<Delivery> Deliveries get; set;

[Key]
public int Id get; set;



Looks like Details.FirstOrDefault() detaches the entity Delivery. The same solution worked with Entity Framework 6. How can I improve my query to get the date from database using only one query (suppressing the warining didn't help)?










share|improve this question

























    up vote
    1
    down vote

    favorite
    1












    I get an exception with DetachedLazyLoadingWarning:




    Error generated for warning 'Microsoft.EntityFrameworkCore.Infrastructure.DetachedLazyLoadingWarning: An attempt was made to lazy-load navigation property 'Product' on detached entity of type 'DeliveryProxy'. Lazy-loading is not supported for detached entities or entities that are loaded with 'AsNoTracking()'.'. This exception can be suppressed or logged by passing event ID 'CoreEventId.DetachedLazyLoadingWarning' to the 'ConfigureWarnings' method in 'DbContext.OnConfiguring' or 'AddDbContext'.




    while trying to query SQL database with Entity Framework Code 2.1



    This is my query:



    var orders = 
    _context
    .Set<Order>()
    .Where(v => v.CompanyId == companyId)
    .Include(v => v.Details)
    .ThenInclude(d => d.Delivery)
    .ThenInclude(v => v.Product)
    .OrderByDescending(v=> v.Details.FirstOrDefault().Delivery.Product.ProductId)
    .ThenByDescending(v=> v.Details.FirstOrDefault().Delivery.Value)
    .ThenByDescending(v => v.CreatedAt)
    .Page(request.Page, request.RowsPerPage);


    Here are entities and relationships:



    public class Order : IEntity<int>

    public int CompanyId get; set;

    public virtual ICollection<OrderDetails> Details get; set;

    [Required]
    public DateTimeOffset CreatedAt get; set;

    [Key]
    public int Id get; set;


    public class OrderDetails : IEntity<int>

    public int OrderId get; set;

    public int DeliveryId get; set;

    [ForeignKey(nameof(OrderId))]
    public virtual Order Order get; set;

    [ForeignKey(nameof(DeliveryId))]
    public virtual Delivery Delivery get; set;

    [Key]
    public int Id get; set;


    public class Delivery : IEntity<int>

    [Required]
    public int ProductId get; set;

    public int Value get; set;

    [ForeignKey(nameof(ProductId))]
    public virtual Product Product get; set;

    [Key]
    public int Id get; set;


    [Table("Products")]
    public class Product : IEntity<int>

    [Required]
    public byte ProductCategoryId get; set;


    public virtual ICollection<Delivery> Deliveries get; set;

    [Key]
    public int Id get; set;



    Looks like Details.FirstOrDefault() detaches the entity Delivery. The same solution worked with Entity Framework 6. How can I improve my query to get the date from database using only one query (suppressing the warining didn't help)?










    share|improve this question























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      I get an exception with DetachedLazyLoadingWarning:




      Error generated for warning 'Microsoft.EntityFrameworkCore.Infrastructure.DetachedLazyLoadingWarning: An attempt was made to lazy-load navigation property 'Product' on detached entity of type 'DeliveryProxy'. Lazy-loading is not supported for detached entities or entities that are loaded with 'AsNoTracking()'.'. This exception can be suppressed or logged by passing event ID 'CoreEventId.DetachedLazyLoadingWarning' to the 'ConfigureWarnings' method in 'DbContext.OnConfiguring' or 'AddDbContext'.




      while trying to query SQL database with Entity Framework Code 2.1



      This is my query:



      var orders = 
      _context
      .Set<Order>()
      .Where(v => v.CompanyId == companyId)
      .Include(v => v.Details)
      .ThenInclude(d => d.Delivery)
      .ThenInclude(v => v.Product)
      .OrderByDescending(v=> v.Details.FirstOrDefault().Delivery.Product.ProductId)
      .ThenByDescending(v=> v.Details.FirstOrDefault().Delivery.Value)
      .ThenByDescending(v => v.CreatedAt)
      .Page(request.Page, request.RowsPerPage);


      Here are entities and relationships:



      public class Order : IEntity<int>

      public int CompanyId get; set;

      public virtual ICollection<OrderDetails> Details get; set;

      [Required]
      public DateTimeOffset CreatedAt get; set;

      [Key]
      public int Id get; set;


      public class OrderDetails : IEntity<int>

      public int OrderId get; set;

      public int DeliveryId get; set;

      [ForeignKey(nameof(OrderId))]
      public virtual Order Order get; set;

      [ForeignKey(nameof(DeliveryId))]
      public virtual Delivery Delivery get; set;

      [Key]
      public int Id get; set;


      public class Delivery : IEntity<int>

      [Required]
      public int ProductId get; set;

      public int Value get; set;

      [ForeignKey(nameof(ProductId))]
      public virtual Product Product get; set;

      [Key]
      public int Id get; set;


      [Table("Products")]
      public class Product : IEntity<int>

      [Required]
      public byte ProductCategoryId get; set;


      public virtual ICollection<Delivery> Deliveries get; set;

      [Key]
      public int Id get; set;



      Looks like Details.FirstOrDefault() detaches the entity Delivery. The same solution worked with Entity Framework 6. How can I improve my query to get the date from database using only one query (suppressing the warining didn't help)?










      share|improve this question













      I get an exception with DetachedLazyLoadingWarning:




      Error generated for warning 'Microsoft.EntityFrameworkCore.Infrastructure.DetachedLazyLoadingWarning: An attempt was made to lazy-load navigation property 'Product' on detached entity of type 'DeliveryProxy'. Lazy-loading is not supported for detached entities or entities that are loaded with 'AsNoTracking()'.'. This exception can be suppressed or logged by passing event ID 'CoreEventId.DetachedLazyLoadingWarning' to the 'ConfigureWarnings' method in 'DbContext.OnConfiguring' or 'AddDbContext'.




      while trying to query SQL database with Entity Framework Code 2.1



      This is my query:



      var orders = 
      _context
      .Set<Order>()
      .Where(v => v.CompanyId == companyId)
      .Include(v => v.Details)
      .ThenInclude(d => d.Delivery)
      .ThenInclude(v => v.Product)
      .OrderByDescending(v=> v.Details.FirstOrDefault().Delivery.Product.ProductId)
      .ThenByDescending(v=> v.Details.FirstOrDefault().Delivery.Value)
      .ThenByDescending(v => v.CreatedAt)
      .Page(request.Page, request.RowsPerPage);


      Here are entities and relationships:



      public class Order : IEntity<int>

      public int CompanyId get; set;

      public virtual ICollection<OrderDetails> Details get; set;

      [Required]
      public DateTimeOffset CreatedAt get; set;

      [Key]
      public int Id get; set;


      public class OrderDetails : IEntity<int>

      public int OrderId get; set;

      public int DeliveryId get; set;

      [ForeignKey(nameof(OrderId))]
      public virtual Order Order get; set;

      [ForeignKey(nameof(DeliveryId))]
      public virtual Delivery Delivery get; set;

      [Key]
      public int Id get; set;


      public class Delivery : IEntity<int>

      [Required]
      public int ProductId get; set;

      public int Value get; set;

      [ForeignKey(nameof(ProductId))]
      public virtual Product Product get; set;

      [Key]
      public int Id get; set;


      [Table("Products")]
      public class Product : IEntity<int>

      [Required]
      public byte ProductCategoryId get; set;


      public virtual ICollection<Delivery> Deliveries get; set;

      [Key]
      public int Id get; set;



      Looks like Details.FirstOrDefault() detaches the entity Delivery. The same solution worked with Entity Framework 6. How can I improve my query to get the date from database using only one query (suppressing the warining didn't help)?







      c# entity-framework ef-code-first entity-framework-core code-first






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 17:58









      Maks Knoski

      61




      61






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote













          You should also be seeing a lot of Client evaluation logging
          warnings. And currently client evaluation doesn't play well with explicit/lazy loading.



          The cause of the client evaluation in this case is the v.Details.FirstOrDefault() expression inside the ordering methods. And the challenge with the current stage of EF Core is to find the supported translatable equivalent LINQ construct.



          In this particular scenario the solution (workaround) is to use intermediate SelectMany projection with Take(1). Replace the part starting from .OrderByDescending(..) up to Page(...) with the following:



          .SelectMany(
          o => o.Details.Select(d => d.Delivery).Take(1).DefaultIfEmpty(),
          (o, d) => new Order = o, Delivery = d )
          .OrderByDescending(v => v.Delivery.ProductId)
          .ThenByDescending(v => v.Delivery.Value)
          .ThenByDescending(v => v.Order.CreatedAt)
          .Select(v => v.Order) // restore the original projection





          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53241864%2fentity-framework-core-2-1-problem-with-detachedlazyloadingwarning%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote













            You should also be seeing a lot of Client evaluation logging
            warnings. And currently client evaluation doesn't play well with explicit/lazy loading.



            The cause of the client evaluation in this case is the v.Details.FirstOrDefault() expression inside the ordering methods. And the challenge with the current stage of EF Core is to find the supported translatable equivalent LINQ construct.



            In this particular scenario the solution (workaround) is to use intermediate SelectMany projection with Take(1). Replace the part starting from .OrderByDescending(..) up to Page(...) with the following:



            .SelectMany(
            o => o.Details.Select(d => d.Delivery).Take(1).DefaultIfEmpty(),
            (o, d) => new Order = o, Delivery = d )
            .OrderByDescending(v => v.Delivery.ProductId)
            .ThenByDescending(v => v.Delivery.Value)
            .ThenByDescending(v => v.Order.CreatedAt)
            .Select(v => v.Order) // restore the original projection





            share|improve this answer


























              up vote
              2
              down vote













              You should also be seeing a lot of Client evaluation logging
              warnings. And currently client evaluation doesn't play well with explicit/lazy loading.



              The cause of the client evaluation in this case is the v.Details.FirstOrDefault() expression inside the ordering methods. And the challenge with the current stage of EF Core is to find the supported translatable equivalent LINQ construct.



              In this particular scenario the solution (workaround) is to use intermediate SelectMany projection with Take(1). Replace the part starting from .OrderByDescending(..) up to Page(...) with the following:



              .SelectMany(
              o => o.Details.Select(d => d.Delivery).Take(1).DefaultIfEmpty(),
              (o, d) => new Order = o, Delivery = d )
              .OrderByDescending(v => v.Delivery.ProductId)
              .ThenByDescending(v => v.Delivery.Value)
              .ThenByDescending(v => v.Order.CreatedAt)
              .Select(v => v.Order) // restore the original projection





              share|improve this answer
























                up vote
                2
                down vote










                up vote
                2
                down vote









                You should also be seeing a lot of Client evaluation logging
                warnings. And currently client evaluation doesn't play well with explicit/lazy loading.



                The cause of the client evaluation in this case is the v.Details.FirstOrDefault() expression inside the ordering methods. And the challenge with the current stage of EF Core is to find the supported translatable equivalent LINQ construct.



                In this particular scenario the solution (workaround) is to use intermediate SelectMany projection with Take(1). Replace the part starting from .OrderByDescending(..) up to Page(...) with the following:



                .SelectMany(
                o => o.Details.Select(d => d.Delivery).Take(1).DefaultIfEmpty(),
                (o, d) => new Order = o, Delivery = d )
                .OrderByDescending(v => v.Delivery.ProductId)
                .ThenByDescending(v => v.Delivery.Value)
                .ThenByDescending(v => v.Order.CreatedAt)
                .Select(v => v.Order) // restore the original projection





                share|improve this answer














                You should also be seeing a lot of Client evaluation logging
                warnings. And currently client evaluation doesn't play well with explicit/lazy loading.



                The cause of the client evaluation in this case is the v.Details.FirstOrDefault() expression inside the ordering methods. And the challenge with the current stage of EF Core is to find the supported translatable equivalent LINQ construct.



                In this particular scenario the solution (workaround) is to use intermediate SelectMany projection with Take(1). Replace the part starting from .OrderByDescending(..) up to Page(...) with the following:



                .SelectMany(
                o => o.Details.Select(d => d.Delivery).Take(1).DefaultIfEmpty(),
                (o, d) => new Order = o, Delivery = d )
                .OrderByDescending(v => v.Delivery.ProductId)
                .ThenByDescending(v => v.Delivery.Value)
                .ThenByDescending(v => v.Order.CreatedAt)
                .Select(v => v.Order) // restore the original projection






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 11 at 17:06

























                answered Nov 11 at 12:05









                Ivan Stoev

                95.7k765118




                95.7k765118



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53241864%2fentity-framework-core-2-1-problem-with-detachedlazyloadingwarning%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    How to read a connectionString WITH PROVIDER in .NET Core?

                    In R, how to develop a multiplot heatmap.2 figure showing key labels successfully

                    Museum of Modern and Contemporary Art of Trento and Rovereto