hibernate/hibernate-orm · error · StrictJpaComplianceViolation

MIXED_POSITIONAL_NAMED_PARAMETERS

MIXED_POSITIONAL_NAMED_PARAMETERS

Error message

Cannot mix ordinal and named parameters

What it means

Error "Cannot mix ordinal and named parameters" thrown in hibernate/hibernate-orm.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/query/hql/internal/SemanticQueryBuilder.java:6233

			@Override
			ParameterStyle withNamed() {
				return NAMED;
			}

			@Override
			ParameterStyle withPositional() {
				return POSITIONAL;
			}
		},
		NAMED {
			@Override
			ParameterStyle withNamed() {
				return NAMED;
			}

			@Override
			ParameterStyle withPositional() {
				throw new StrictJpaComplianceViolation(
						"Cannot mix ordinal and named parameters",
						StrictJpaComplianceViolation.Type.MIXED_POSITIONAL_NAMED_PARAMETERS
				);
			}
		},
		POSITIONAL {
			@Override
			ParameterStyle withNamed() {
				throw new StrictJpaComplianceViolation(
						"Cannot mix positional and named parameters",
						StrictJpaComplianceViolation.Type.MIXED_POSITIONAL_NAMED_PARAMETERS
				);
			}

			@Override
			ParameterStyle withPositional() {
				return POSITIONAL;
			}

View on GitHub (pinned to fad1729dce)

Solutions

  1. A query cannot mix ordinal (?1) and named (:name) parameters. Convert all parameters to one style.

When it happens

Trigger: Named and ordinal parameters are mixed in one query: Cannot mix ordinal and named parameters

Common situations: HQL/criteria queries combining ':name' and '?1' style parameters, which Hibernate forbids.


AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/5f5bb797a7c086ca. Report an issue: GitHub.