[CSHARP-2744] Consider to restore(or modify) the previously removed logic or be sure that it doesn't cause a reason of wrong nested `Any`s Created: 16/Sep/19  Updated: 06/Nov/19  Resolved: 06/Nov/19

Status: Closed
Project: C# Driver
Component/s: Linq
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dmitry Lukyanov (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to CSHARP-2801 Nested .Any() behavior changed in 2.8.0 Closed
is related to CSHARP-1356 LINQ .Any(x => !list.Contains(x)) tra... Closed
is related to CSHARP-2699 Wrong queries for nested filters Closed

 Description   

As it was noticed in the ticket CSHARP-2699, the changes which were done in the scope of CSHARP-1356 led to the wrong nested `Any`s in some advance cases.
See this thread: https://github.com/DmitryLukyanov/mongo-csharp-driver/pull/53#discussion_r317409755

Previously `VisitPipeline` method (https://github.com/DmitryLukyanov/mongo-csharp-driver/pull/13#discussion_r247197507) has been removed because we didn't find any query which could be affected by this removing, but since now we've met it, so probably we need to look at the change(removing `VisitPipeline`) from the ticket `CSHARP-1356` one more time.



 Comments   
Comment by Dmitry Lukyanov (Inactive) [ 06/Nov/19 ]

It has been implemented in the scope of CSHARP-2801

Generated at Wed Feb 07 21:43:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.