Class ArgumentTypesValidator
java.lang.Object
org.hibernate.query.sqm.produce.function.ArgumentTypesValidator
- All Implemented Interfaces:
ArgumentsValidator
Typechecks the arguments of HQL functions based on the assigned JDBC types.
- Author:
- Gavin King
-
Constructor Summary
ConstructorsConstructorDescriptionArgumentTypesValidator(ArgumentsValidator delegate, FunctionParameterType... types) -
Method Summary
Modifier and TypeMethodDescriptionPretty-print the signature of the argument list.voidvalidate(List<? extends SqmTypedNode<?>> arguments, String functionName, TypeConfiguration typeConfiguration) We do an initial validation phase with just the SQM tree, even though we don't have all typing information available here (in particular, we don't have the final JDBC type codes for things with converters) because this is the phase that is run at startup for named queries, and can be done in an IDE.voidvalidateSqlTypes(List<? extends SqlAstNode> arguments, String functionName) This is the final validation phase with the fully-typed SQL nodes.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.hibernate.query.sqm.produce.function.ArgumentsValidator
validate
-
Constructor Details
-
ArgumentTypesValidator
-
-
Method Details
-
validate
public void validate(List<? extends SqmTypedNode<?>> arguments, String functionName, TypeConfiguration typeConfiguration) We do an initial validation phase with just the SQM tree, even though we don't have all typing information available here (in particular, we don't have the final JDBC type codes for things with converters) because this is the phase that is run at startup for named queries, and can be done in an IDE.- Specified by:
validatein interfaceArgumentsValidator
-
validateSqlTypes
This is the final validation phase with the fully-typed SQL nodes. Note that these checks are much less useful, occurring "too late", right before we execute the query and get an error from the database. However, they help in the sense of (a) resulting in more consistent/understandable error messages, and (b) protecting the user from writing queries that depend on generally-unportable implicit type conversions happening at the database level. (Implicit type conversions between numeric types are portable, and are not prohibited here.)- Specified by:
validateSqlTypesin interfaceArgumentsValidator
-
getSignature
Description copied from interface:ArgumentsValidatorPretty-print the signature of the argument list.- Specified by:
getSignaturein interfaceArgumentsValidator
-