-
Notifications
You must be signed in to change notification settings - Fork 383
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
Support the new BCL DateOnly and TimeOnly structs #1361
Comments
Please note that the final names for these types are |
They are coming in .NET 6 Preview 4. |
@lauxjpn yes. Note that it may be a good idea to hold off here (and in Npgsql) until support is added in EF Core itself (dotnet/efcore#24506, dotnet/efcore#24507), this way the specification tests will already be added upstream. I hope to make that happen pretty quickly after the preview4 release. |
Any news? Dotnet version: 6.0.100-preview.7.21379.14 |
FYI support in EF Core has been added for Sqlite, including functional tests. |
We will implement it in the near future. |
Using EF 6.05 and the same error as @uzairali001 on VS2022 for Microsoft SQL 2019 |
@BrokenShoeLace If you're using MS SQL then please look at dotnet/efcore#24507. |
Thanks for the link but ut doesnt address my issue: TimeOnly is not DateOnly |
@BrokenShoeLace Please clarify: Are you using |
Microsoft.EntityFrameworkCore.SqlServer |
Microsoft.EntityFrameworkCore.SqlServer doesn't support DateOnly/TimeOnly, because the underlying SqlClient doesn't - the issue tracking that is dotnet/SqlClient#1009. Once that's done, support in EF Core can be enabled in dotnet/efcore#24507. This is the respository for the Pomelo MySQL provider, so not related to SQL Server. |
New DateOnly and TimeOnly structs are being introduced to .NET 6 as alternatives to DateTime (dotnet/runtime#49036). MySqlConnector issue: mysql-net/MySqlConnector#963.
The text was updated successfully, but these errors were encountered: