HHH-18960 Hibernate Processor - when query parameter allows multiple value binding parameter in generated query should be collection

[cigaly]

Jira issue HHH-18960

Currently when named query parameter allows multiple value binding (like parameters for in), in generated query it is represented as raw type instead of List (or, possibly, Collection). Same problem is present when generating meta model class for Jakarta Data repository.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

---

[gavinking]

LGTM

[gavinking]

Merged, thanks so much, @cigaly

[cigaly]

You're welcome!

[cigaly]

@gavinking It seems that this solution can not work properly due to (org.hibernate.query.hql.internal.SemanticQueryBuilder)

	private SqmExpression<?> visitFinalFunctionArgument(ParseTree expression) {
		// the final argument to a function may accept multi-value parameter (varargs),
		// 		but only if we are operating in non-strict JPA mode
		parameterDeclarationContextStack.push( () -> !creationOptions.useStrictJpaCompliance() );
...

So, when useStrictJpaCompliance is set to false (by default), every parameter will allow multi value binding. I'm afraid that this can make more troubles than original problem I've tried to solve :-(

[gavinking]

Ah okey good, can you send me you test case, please?

[cigaly]

@gavinking Here it is - PR #9475
Simply added named query in existing test case