-
Notifications
You must be signed in to change notification settings - Fork 365
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
Compatibility of ImmutableType with custom functions and typed paramaters #430
Comments
The problem with However, we could investigate whether we could provide the user a |
We're getting pretty far with this using the |
metadataBuilder.applySqlFunction
requires aFunctionReturnTypeResolver
which in turns require types to extend fromReturnableType
metadataBuilder.applySqlFunction
requires aFunctionArgumentTypeResolver
which in turns require types to extend fromMappingModelExpressible<?>
, like for exampleBasicValuedMapping
is.TypedParameterValue
requires aBindableType
, like for exampleSqmExpressible
is.I think in order to support custom functions and typed parameters the following signature changes need to be made:
MutableType
additionally extend fromReturnableType<T>
. This only allows the introduction ofgetPersistenceType
andgetJavaType
atMutableType
level.ImmutableType
extend fromUserType<T>, BindableType<T>, SqmExpressible<T>, BasicValuedMapping, ReturnableType<T>
instead ofMutableType
, likeMutableType
.Whilst the new type system of Hibernate 6.0 is one of its key features, I am currently not really seeing it. It could well be possible that more changes will be required. At this point we may want to just go for
BasicType
extensions instead ... Theorg.hibernate.usertype.UserType
hierarchy seems fairly limited in its current abilities.The text was updated successfully, but these errors were encountered: