[CSHARP-3598] LINQ3: Use the IMongoQueryable interface in LINQ3 also Created: 21/Apr/21 Updated: 09/Jul/21 Resolved: 22/Apr/21 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | LINQ3 |
| Affects Version/s: | None |
| Fix Version/s: | 2.14.0 |
| Type: | Task | Priority: | Unknown |
| Reporter: | Robert Stam | Assignee: | Robert Stam |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Epic Link: | CSHARP-2608 | ||||||||||||||||||||
| Description |
|
LINQ3 currently is based entirely on the standard `IQueryable` interface. LINQ2 defined a custom `IMongoQueryable` sub interface that is used for most scenarios that are MongoDB specific. Both approaches are valid in their own way, but for backward compatibility reasons we should make LINQ3 also use the `IMongoQueryable` interface. |
| Comments |
| Comment by Robert Stam [ 21/Apr/21 ] |
|
This will be a little tricky because LINQ3 uses an internal `IMongoQueryable` interface but since it's not public it's not part of the public API and it is used in a different way. The two interfaces with the same name will have to be reconciled. |