[CSHARP-2708] Verify scenarios involving string.IsNullOrEmpty with or without null coalescing in argument Created: 23/Aug/19 Updated: 28/Oct/23 Resolved: 13/Oct/21 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | LINQ3 |
| Affects Version/s: | None |
| Fix Version/s: | 2.14.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Richard Collette | Assignee: | Robert Stam |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | rp-track | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
This works
But in the where clause of a LINQ query
I get the error
|
| Comments |
| Comment by Robert Stam [ 13/Oct/21 ] | ||||
|
This issue has been fixed in the new LINQ provider (known as LINQ3) which will be included in the upcoming 2.14 release. Configure your MongoClientSettings to use LinqProvider.V3 if you want to use this functionality. To configure a client to use the LINQ3 provider use code like the following
| ||||
| Comment by Githook User [ 13/Oct/21 ] | ||||
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: | ||||
| Comment by Robert Stam [ 08/Oct/21 ] | ||||
|
Tested Aggregate using Match and Project. Tested AsQueryable using Select and Where. Note that some scenarios require using `$expr` in the `$match` filter because they can't be expressed using filter language alone. | ||||
| Comment by Richard Collette [ 23/Aug/19 ] | ||||
|
Actually, it does not work in a .Match() method expression either. |