Delete methods behave differently after upgrade to 3.5.4

[mhankus]

I've just upgraded my spring-boot app to 3.5.6, which updates also spring-data to 3.5.4
After the upgrade, our methods

which look like

 long deleteBySomeAttr(int val);

result in error

Null return value from advice does not match primitive return type for: ...

I think it can be related to 72dd53a#diff-dc360e9f00538d98dbdafa414534e321b68fe0e293fbefe37bacdb5e76cd3315R58-L411

where return value was changed from

	return jpaQuery.getQueryMethod().isCollectionQuery() ? resultList : resultList.size();

to

       return collectionQuery ? resultList : CollectionUtils.firstElement(resultList);

so when no value is deleted, null is returned, and is not converted to 0 (we have "long" as return value)

This is a breaking change in 3.5.x release. I'm not sure which is the correct way of solving this problem. Is it a bug, or return of "long" is not allowed from now on.

[mirkoseifert]

I have the same problem. I've upgraded Spring Boot from 3.5.5 to 3.5.6 and I have a method:

long deleteByCreationTimeBefore(Instant creationTime);

When this method is called, I get the following exceptions:

org.springframework.dao.IncorrectResultSizeDataAccessException: Delete query returned more than one element: expected 1, actual 2

[oscarfanchin]

hi, have you tried with the boxed Long or Integer value?, it is a known issue fixed in the current snapshot.

[mirkoseifert]

It works with Long and Integer, but fails with long or int.

I can use this as a workaround. Thanks!

[123Haynes]

duplicate of #4015

Workaround is either used boxed types, or downgrade for now.
In Spring Boot you can simply set this property until the 3.5.7 release next month:
<spring-data-bom.version>2025.0.3</spring-data-bom.version>