Skip to content
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

Merged
merged 4 commits into from
Mar 5, 2024
Merged

Conversation

spencerjanssen
Copy link
Contributor

Code thanks to @jberryman

We've been using this code in production at my employer since June 2023 without issue.

Copy link
Member

@psibi psibi left a 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 ?

@spencerjanssen
Copy link
Contributor Author

@psibi done! Also bumped the version number up to 0.3.0 due to the changes in #48

@psibi psibi merged commit 8b9f41f into fpco:master Mar 5, 2024
1 check passed
@psibi
Copy link
Member

psibi commented Mar 5, 2024

Pushed a release to Hackage, thanks!

type I16 = Int
#endif

-- FIXME fail with Randomized with seed 1862667972
Copy link
Contributor

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?

Copy link
Contributor Author

@spencerjanssen spencerjanssen Mar 5, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants