some refinements.

There's a difference in what the query needs to look like using dto vs. interface projections where the former does not allow column aliases and the latter requires them.

Author: christophstrobl

spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/query/AbstractStringBasedJpaQuery.java

@@ -119,7 +119,13 @@ public Query doCreateQuery(JpaParametersParameterAccessor accessor) {
 
 		Sort sort = accessor.getSort();
 		ResultProcessor processor = getQueryMethod().getResultProcessor().withDynamicProjection(accessor);
-		String sortedQueryString = getSortedQueryString(sort, processor.getReturnedType());
+
+		String sortedQueryString = null;
+		if(querySortRewriter.equals(NoOpQuerySortRewriter.INSTANCE) && accessor.findDynamicProjection() != null && !accessor.findDynamicProjection().isInterface()) {
+			sortedQueryString = getSortedQueryString(new ProjectingSortRewriter(), query, sort, processor.getReturnedType());
+		} else {
+			 sortedQueryString = getSortedQueryString(sort, processor.getReturnedType());
+		}
 
 		Query query = createJpaQuery(sortedQueryString, sort, accessor.getPageable(), processor.getReturnedType());
 
@@ -134,6 +140,10 @@ String getSortedQueryString(Sort sort, ReturnedType returnedType) {
 		return querySortRewriter.getSorted(query, sort, returnedType);
 	}
 
+	private static String getSortedQueryString(QuerySortRewriter rewriter, DeclaredQuery query, Sort sort, ReturnedType returnedType) {
+		return rewriter.getSorted(query, sort, returnedType);
+	}
+
 	@Override
 	protected ParameterBinder createBinder() {
 		return createBinder(query);

spring-data-jpa/src/test/java/org/springframework/data/jpa/repository/EclipseLinkUserRepositoryFinderTests.java

@@ -36,4 +36,8 @@ void executesNotInQueryCorrectly() {}
 	@Override
 	void executesInKeywordForPageCorrectly() {}
 
+	@Disabled
+	@Override
+	void rawMapProjectionWithEntityAndAggregatedValue() {}
+
 }

spring-data-jpa/src/test/java/org/springframework/data/jpa/repository/sample/UserRepository.java

@@ -735,10 +735,10 @@ List<String> findAllAndSortByFunctionResultNamedParameter(@Param("namedParameter
 	@UserRoleCountProjectingQuery
 	Page<UserRoleCountDtoProjection> dtoProjectionEntityAndAggregatedValue(PageRequest page);
 
-	@UserRoleCountProjectingQuery
+	@Query("select u as user, count(r) as roleCount from User u left outer join u.roles r group by u")
 	List<UserRoleCountInterfaceProjection> interfaceProjectionEntityAndAggregatedValue();
 
-	@UserRoleCountProjectingQuery
+	@Query("select u as user, count(r) as roleCount from User u left outer join u.roles r group by u")
 	List<Map<String, Object>> rawMapProjectionEntityAndAggregatedValue();
 
 	@UserRoleCountProjectingQuery
@@ -747,7 +747,7 @@ List<String> findAllAndSortByFunctionResultNamedParameter(@Param("namedParameter
 	Window<User> findBy(OffsetScrollPosition position);
 
 	@Retention(RetentionPolicy.RUNTIME)
-	@Query("select u AS user, count(r) AS roleCount from User u left outer join u.roles r group by u")
+	@Query("select u, count(r) from User u left outer join u.roles r group by u")
 	@interface UserRoleCountProjectingQuery {}
 
 	interface RolesAndFirstname {

src/main/antora/modules/ROOT/pages/repositories/projections.adoc

@@ -40,6 +40,13 @@ This query gets rewritten to `SELECT new UserDto(u.firstname, u.lastname) FROM U
 This query gets rewritten to `SELECT new UserDto(u.firstname, u.lastname) FROM USER u`.
 ====
 
+[WARNING]
+====
+JPQL constructor expressions must not contain aliases for selected columns.
+While `SELECT u as user, count(u.roles) as roleCount FROM USER u ...` is a valid usecase for interface based projections that rely on column names from the returned `Tuple`, the same construct is invalid when requesting a DTO where it needs to be `SELECT u, count(u.roles) FROM USER u ...`. +
+Some persistence providers may be lenient about this, others not.
+====
+
 Repository query methods that return a DTO projection type (a Java type outside the domain type hierarchy) are subject for query rewriting.
 If an `@Query`-annotated query already uses constructor expressions, then Spring Data backs off and doesn't apply DTO constructor expression rewriting.