Use FeatureNotSupportedException instead of RuntimeException where appropriate
#145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e appropriate HIBERNATE-45
vbabanin
approved these changes
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We no longer have
NotYetImplementedException- we replaced it withFeatureNotSupportedException, which no longer expresses whether we are planning to support a particular feature.FeatureNotSupportedExceptionis not a temporary one - some Hibernate ORM / MQL features will never be supported. This makes HIBERNATE-45 irrelevant, and I initially wanted to just close it. But then I noticed a few places where we useRuntimeException, butFeatureNotSupportedExceptionseems like a better fit there, so I changed them.HIBERNATE-45