-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter on nullable DateOnly seems not supported #2912
Comments
@ArnaudB88 'DateOnly' and 'TimeOnly' are two new C# types added since .NET 6. ODL hasn't supported them by default owing to the target framework setting. We'd like to enable it in the next major version. Before that, ODL has its own 'Date' and 'TimeOfDay' types that you can use. |
Hi @ArnaudB88. This is a known feature gap. I'll go ahead and close this issue and use #2293 to track the work required to support the |
Hi @gathogojr it seems the item you're referring to has been around for more than two years and still there is no support for the DateOnly (and TimeOnly) types in a query filter. We've gone and create a copy of the code for our private feed that simply adds two additional if-statements to the to the Is there any chance this can be added any time soon? I'd make a PR for just the change I made, but since this just fixes the NotSupportException when creating a filter this doesn't quite seem to cover the whole "Deprecate 'TimeOfDay' and 'Date' types in favor" case. |
#3078 supports the DateOnly and TimeOnly in OData.Core and We'd move forward to fully support it in OData.Client and OData Connected Service. |
I want to filter on a nullable DateOnly type field. Currently this throws an exception.
Assemblies affected
Microsoft.OData.Core.dll v7.20
Reproduce steps
Date
fieldDateOnly?
since .NET8 is usedStartDate ge 2024-03-29
Expected result
Query would return a result
Actual result
I am getting the following error:
Additional detail
This is possibly related with the feature request #2293
The text was updated successfully, but these errors were encountered: