Skip to content

Support for MySQL and MSSQL #1535

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

Merged
merged 17 commits into from
Mar 29, 2023
Merged

Support for MySQL and MSSQL #1535

merged 17 commits into from
Mar 29, 2023

Conversation

DavideD
Copy link
Member

@DavideD DavideD commented Mar 27, 2023

Fix #1538
Fix #1533
Fix #1528

It requires the latest ORM snapshot but I'm going to merge it anyway

@DavideD DavideD force-pushed the 1533 branch 3 times, most recently from 27c96e8 to fc34d20 Compare March 27, 2023 20:53
DavideD added 11 commits March 28, 2023 11:26
…TimeType

It fails in MSSQL and it seems related to a bug in ORM
It shouldn't rely on the order of the elements in the collection
Split it in smaller and simpler test.
It easier to debug and understand what's going on this way.
We often need to compare what we do with ORM.
Having the JDBC drivers and the configuration ready, saves us some time.
DavideD added 2 commits March 28, 2023 12:14
The Vert.x MSSQL client doesn't support it and it's unclear how
one would use it.
Except for MySQL because the Vert.x client doesn't like when we try
to save temporal types with a time zone.
@DavideD DavideD merged commit b5c8fe7 into hibernate:main Mar 29, 2023
@DavideD
Copy link
Member Author

DavideD commented Mar 29, 2023

Merged. There is no point in keeping this a PR
But it requires the latest ORM snapshot

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.

Saving timestamps doesn't work with the latest ORM snapshot Add support for MSSQL Add support for MySQL
1 participant