-
Notifications
You must be signed in to change notification settings - Fork 22
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
Compatibility with text 2 #58
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, can you update the CHANGELOG ?
Pushed a release to Hackage, thanks! |
type I16 = Int | ||
#endif | ||
|
||
-- FIXME fail with Randomized with seed 1862667972 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened to this FIXME?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test/Main.hs:347:15:
1) Database.ODBC.SQLServer, Conversion to SQL, QuickCheck roundtrip: HS=Datetime2, SQL=datetime2
uncaught exception: ODBCException
UnsuccessfulReturnCode "odbc_SQLExecDirectW" (-1) "[Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Conversion failed when converting date and/or time from character string." (Just "22007")
(after 15 tests)
Datetime2 {unDatetime2 = 1796-07-15 23:59:60.9660284}
I guess SQL Server doesn't like the leap second on a day that shouldn't have leap seconds?
EDIT: Actually, SQL Server doesn't support leap seconds at all.
Code thanks to @jberryman
We've been using this code in production at my employer since June 2023 without issue.