-
Notifications
You must be signed in to change notification settings - Fork 933
NH-3078 removing a datetime to timespan conversion #635
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
Conversation
Of course it will have to be rebased without the npgsql changes if we want to merge this. |
It does not work for SQLite, so it will require the fix similar to SqlServerCe |
|
This is in line with the |
This fix makes |
Does not work for Oracle |
Yes, I was expecting failure for |
For Oracle, that is not the tests I would have expected which fail. SQLite demonstrates some providers are not ready for the switch. We may override So even if this change would be cleaner for databases like SqlServer or PostgreSql with up-to-date Npgsql, I do not think it is worth it, due to the high likeliness of regressions for some old or untested databases. |
But there are no failures... Strange. Going to check the tests. |
Not based on the "good" branch, it has not used the new npgsql driver. Changing that. |
2fb28f3
to
7e50652
Compare
"A more robust solution" in my mind would be the following;
|
Looking to do that in NH-4017.
You mean driver rather than dialect? Anyway the
Had impacted
So it should be fine provided we left
For set, sure. For get, it looks to me current code, which tries casting, is more reliable than using some declarative property. |
Closing in favor of #637. Feel free to reopen, if needed. |
NH-3078, as per #631 discussion.