Simplify inference of the SupportedDbKind and avoid NoClassDefFoundError on CommunityDatabase
#50146
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.
Second commit is the one that matters.
We used to try to derive it from the dbKind string, falling back to
attempting to interpret the Hibernate ORM "DB Product Name".
But the "DB Product Name" can only be set in situation where we have a
dbKind string already, so the fallback is pointless.
Since the fallback also has problems (use of
CommunityDatabase
which isnot necessarily in the classpath), we might as well remove it.