Changed confusing negative wording on 'Mapped Superclasses' doc #11775
Conversation
This file contains 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
SenseException
approved these changes
Dec 30, 2024
|
Thank you @Floriansylvain |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As I was reading more about Inheritance Mapping, I've come across this turn of phrase that's a bit confusing, especially if english is not your first language. Or maybe it's just me, in which case I'd understand if you refused this PR.
Otherwise, I've simply used a slightly clearer negation that makes it explicit (perhaps only in my opinion) that Mapped Superclasses don't need an ID column.