You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.
It seems like adding support for ZonedDateTime is gated by there currently not being a way to map to two database fields in Dapper.
I've made a post on the Dapper repo to see if there is any interest in reviving that question, and so I figured I'd cross post here. If it gets any traction over at Dapper, it feels like it would then be pretty simple to add here. (I'd be willing to take a first crack at it).
Of course, if anyone has any thoughts on how to do this without a change to Dapper, that would be interesting. Currently, though it seems like the only way is to create an intermediary type that breaks apart the ZonedDateTime type.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems like adding support for ZonedDateTime is gated by there currently not being a way to map to two database fields in Dapper.
I've made a post on the Dapper repo to see if there is any interest in reviving that question, and so I figured I'd cross post here. If it gets any traction over at Dapper, it feels like it would then be pretty simple to add here. (I'd be willing to take a first crack at it).
Dapper issue
Of course, if anyone has any thoughts on how to do this without a change to Dapper, that would be interesting. Currently, though it seems like the only way is to create an intermediary type that breaks apart the ZonedDateTime type.
The text was updated successfully, but these errors were encountered: