Nested nullable projection

[yanick4sh]

Today I tried to upgrade the spring boot version in my application.
I upgrade spring-boot from 3.3.5 to 3.5.4, but I faced regressions (or new wanted behavior ?) with nested projection.

I have a projection with another nested projection :

public interface MyProjection {
    String getReference();
    MyNestedProjection getType();
}

public interface MyNestedProjection {
    String getReference();
}

In my @Entity, type is an optional @ManyToOne.
I use MyProjection with QuerydslPredicateExecutor like that :

jpaCrudRepository.findBy(
    new BooleanBuilder(),
    q -> q.as(MyProjection.class).all()
)

In spring-boot 3.3.5 to 3.4.8 if type is null I still have my projected entity with "type" set to null (left join behavior)
In spring-boot 3.5.0 to 3.5.4 if type is null I don't have my projected entity (inner join behavior)

I didn't read anything about this change in any release note (I may have missed something...)

[mp911de]

The related issue is #3716 and it was mentioned in our 3.5.0 release notes.

I'm not quite sure I understand your ask. The projection returns null if the many-to-one object is null and it returns a nested projection if the many-to-one object is present.

It would be helpful to see the problem in action if you could provide a minimal yet complete sample that reproduces the problem.
You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.