count query issue in spring-data-jpa-2.5.11

[lavanya2290]

When we check our native query an issue comes
the count uery changes from select count(*) from tablename to select count(order) from tablename.

2.5.9...2.5.11#diff-7d36425745042f8c27507657de795fd7cf1d546da6a740fd00d86add46f81ed4R530

[lavanya2290]

[lavanya2290]

Matcher matcher = COUNT_MATCH.matcher("SELECT * FROM context ORDER BY time");
String countQuery;

	if (countProjection == null) {

		String variable = matcher.matches() ? matcher.group(VARIABLE_NAME_GROUP_INDEX) : null;
		boolean useVariable = StringUtils.hasText(variable) //
				&& !variable.startsWith(" new") //
				&& !variable.startsWith("count(") //
				&& !variable.contains(",") //
				&& !variable.contains("*");

		String complexCountValue = matcher.matches() && StringUtils.hasText(matcher.group(COMPLEX_COUNT_FIRST_INDEX))
				? COMPLEX_COUNT_VALUE
				: COMPLEX_COUNT_LAST_VALUE;

		String replacement = useVariable ? SIMPLE_COUNT_VALUE : complexCountValue;
		countQuery = matcher.replaceFirst(String.format(COUNT_REPLACEMENT_TEMPLATE, replacement));

[gregturn]

#2514 has been backported to 2.5.x. Does this issue persist @lavanya2290 ?

[lavanya2290]

in 2.5.13 spring boot which uses 2.5.11 issue is there.
also is there any new release I can check

[Axinet]

#2495 is still open, so the only option as for now is downgrade to spring-data-jpa 2.5.10

[gregturn]

Support for 2.5.x ended back in April. I'm closing this ticket for now. If you are still running into this issue on 2.6.x+, then please open a new ticket with details.

[lavanya2290]

Issue is still there in mentioned version

…

On Wed, May 4, 2022, 9:20 PM Greg L. Turnquist ***@***.***> wrote: #2514 <#2514> has been backported to 2.5.x. Does this issue persist @lavanya2290 <https://github.com/lavanya2290> ? — Reply to this email directly, view it on GitHub <#2511 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJDMHLXCOY4YY2WUZSAT4TVIKME3ANCNFSM5UOXLICQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Axinet]

As mentioned above, support for 2.5.x line has ended in April. You either have to upgrade to 2.6 line, or if you can't, revert to previous version in 2.5 line without that bug.
Recent 2.6.x versions don't have this bug any longer.