-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Translate DateTimeOffset.ToUnixTime[Seconds|Milliseconds] #28925
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
community-contribution
customer-reported
good first issue
This issue should be relatively straightforward to fix.
type-enhancement
Milestone
Comments
ajcvickers
added
good first issue
This issue should be relatively straightforward to fix.
area-query
labels
Aug 31, 2022
Please assign it to me |
@Marusyk Feel free to submit a PR. Note that EF7 is closed for new features, so the PR should target the |
bricelam
pushed a commit
to Marusyk/efcore
that referenced
this issue
Mar 20, 2023
bricelam
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Mar 20, 2023
bricelam
pushed a commit
to Marusyk/efcore
that referenced
this issue
Mar 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
community-contribution
customer-reported
good first issue
This issue should be relatively straightforward to fix.
type-enhancement
ToUnixTime* methods on DateTimeOffset can be translated in SQL Server as
DATEDIFF(second|millisecond, '1970-01-01T00:00:00.000', [Date])
.This can even be done today verbosely with
EF.Functions
asEF.Functions.DateDiffSecond(DateTimeOffset.UnixEpoch, date)
. It would be nice if translation of ToUnixTimeSeconds/ToUnixTimeMilliseconds was supported natively.The text was updated successfully, but these errors were encountered: