Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Nested nullable projection #3988

Closed as not planned
Closed as not planned
@yanick4sh

Description

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...)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /