Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-4859

Support nested AsQueryable

    • Type: Icon: New Feature New Feature
    • Resolution: Done
    • Priority: Icon: Unknown Unknown
    • 2.24.0
    • Affects Version/s: 2.22.0
    • Component/s: LINQ3
    • None
    • Fully Compatible
    • Needed
    • Hide
      1. What would you like to communicate to the user about this feature?
        2. Would you like the user to see examples of the syntax and/or executable code and its output?
        3. Which versions of the driver/connector does this apply to?

      Not sure whether to document this or not.

      A human writing a LINQ query would normally never use a nested AsQueryable, which though legal is totally unnecessary and kind of silly. This feature was added to support the EF Core Provider.

      Show
      What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to? Not sure whether to document this or not. A human writing a LINQ query would normally never use a nested AsQueryable, which though legal is totally unnecessary and kind of silly. This feature was added to support the EF Core Provider.

      Consider supporting nested AsQueryable, for example:

      collection.AsQueryable().Select(x => x.List.AsQueryable().Count()) 
      

      and treat is as equivalent to:

      collection.AsQueryable().Select(x => x.List.Count()) 
      

      Using nested AsQueryable in this way doesn't make much sense, but it is legal C#.

      The primary motivation for this change is to support the MongoDB EF Core Provider. Apparently EF Core inserts this call to AsQueryable and rewrites the expressions using the equivalent Queryable methods for each Enumerable method. Why it does this doesn't make much sense, but if we were to support this odd usage in the C# driver's LINQ provider it would make implementing the MongoDB EF Core Provider easier (otherwise the MongoDB EF Core Provider would have to undo what EF Core did to remove the unecessary AsQueryable).

            Assignee:
            robert@mongodb.com Robert Stam
            Reporter:
            robert@mongodb.com Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: