Remove floating point types from types advertised to support precision & scale #4559
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.
Related to HBX-1408
This PR fixes an inconsistency in Java entities generation. Indeed
hibernate-tools
generate entities whose floating point type fields are annotated with a@Type
withscale
andprecision
parameters. However these parameters are not relevant and generateIllegalArgumentException
as per https://github.com/hibernate/hibernate-orm/blob/7c58fe9a16eb15e5d1432e4bb3434c89cf214e16/hibernate-core/src/main/java/org/hibernate/dialect/Dialect.java#L5097-L5112.This PR changes
JdbcToHibernateTypeHelper
so thattypeHasScaleAndPrecision
do not advertise these types to support scale and precision.