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

Removes @Inheritance from JPABaseEntity #498

Conversation

froque
Copy link
Member

@froque froque commented Dec 6, 2023

Fixes Hibernate warning:
HHH000503: A class should not be annotated with both @Inheritance and @MappedSuperclass. @Inheritance will be ignored for: com.premiumminds.billy.core.persistence.entities.jpa.JPABaseEntity

https://hibernate.atlassian.net/browse/HHH-13217
Don't throw exception if both @MappedSuperclass and @Inheritance are used

Fixes #164

Fixes Hibernate warning:
HHH000503: A class should not be annotated with both @Inheritance and @MappedSuperclass. @Inheritance will be ignored for: com.premiumminds.billy.core.persistence.entities.jpa.JPABaseEntity

https://hibernate.atlassian.net/browse/HHH-13217
Don't throw exception if both @MappedSuperclass and @Inheritance are used
@froque froque requested a review from thenmaster January 9, 2024 09:46
@froque froque merged commit 67e8940 into master Jan 9, 2024
1 check passed
@froque froque deleted the 164-a-class-should-not-be-annotated-with-both-inheritance-and-mappedsuperclass branch January 9, 2024 10:09
thenmaster pushed a commit that referenced this pull request Jan 10, 2024
country modules

This annotation was previously being set in JPABaseEntity but was
removed in #498. This change resulted in a change to the schema required
by the application that was only detected when a client application was
updated since the schema used during tests is generated from the code
meaning it is always correct.

Adding the annotation back to all entities that are extended in the
various submodules resolves this problem since hibernate once again
knows how the schema of the application should be assembled
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.

A class should not be annotated with both @Inheritance and @MappedSuperclass
2 participants