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

Upgrade to Hibernate 5.2 cause Attempt to resolve foreign key metadata from JDBC metadata failed to find column mappings for foreign key #6186

Closed
top-bettercode opened this issue Jun 19, 2016 · 4 comments

Comments

@top-bettercode
Copy link

top-bettercode commented Jun 19, 2016

Spring Boot 1.4.0.BUILD-SNAPSHOT Upgrade to Hibernate 5.2.0 cause Attempt to resolve foreign key metadata from JDBC metadata failed to find column mappings for foreign key(detail).
This is a Hibernate bug https://hibernate.atlassian.net/browse/HHH-10802.

Upgrade to Hibernate 5.2.0 is not good,I think.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 19, 2016
@wilkinsona
Copy link
Member

wilkinsona commented Jun 19, 2016

The fix versions on the Hibernate issue (5.2.1 and 5.1.1) are interesting. I was under the impression that 5.2 essentially replaced 5.1 and 5.1 wasn't going to be maintained. If 5.1 is going to be maintained, I think we should strongly consider using. It doesn't require Java 8 and, having lived with it for a few days, moving to Java 8 for such a widely used dependency now feels too aggressive

Unfortunately, dropping back to 5.1 doesn't look like it'll help with this specific issue and would require our RC to wait for Hibernate 5.1.1 and Spring Framework 4.3.1.

@snicoll
Copy link
Member

snicoll commented Jun 19, 2016

5.1.1 was due in March 9th and 5.2.1 is due in June 29th. I guess they are going to be co-released and that's definitely after our current RC. We can have a CI goal on 5.2.x and stick with 5.1 that is more aligned with our own system requirements. In any case, we integrate with a gazillion of libs now so delaying our RC for that issue seems a bit overkill.

On the other hand, Spring Framework 4.3.1 brings several important changes regarding Hibernate 5.2 support (remember: Hibernate 5.0 and 5.1 doesn't work anymore due to a binary incompatible change on the Hibernate side). If we go with 4.3.0 we have no other choice to stick with 5.2

@wilkinsona
Copy link
Member

9th March? Ouch.

Despite the fix version on the Hibernate issue, an answer to the Stack Overflow question says that 5.1.0 is not affected so it could be an option once Spring Framework 4.3.1 is out. I'm still leaning towards using a version of Hibernate that works with Java 7 out of the box.

@wilkinsona
Copy link
Member

We're going to drop back to Hibernate 5.0.x (see #6198).

@wilkinsona wilkinsona removed the status: waiting-for-triage An issue we've not yet triaged label Jun 21, 2016
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

No branches or pull requests

4 participants