AssertionError in org.hibernate.sql.results.graph.Initializer.getResolvedInstance()

Description

Activity

Show:

RM January 15, 2025 at 2:39 PM

I second that, we have the same issue.

You can solve the AssertionError by removing the fetch in “left join fetch” and adding eager above the collections. But that is not what we want and with other queries just adding eager triggers another AssertionError which doesn’t occur with lazy.

Most of the time we just want it to be lazy except in the query with the fetch.

Issue also affects 6.6.4.

Maciej W. January 7, 2025 at 3:59 PM

There is issue with the same error but approach is a bit different so I’ve decided to create new bug.

Maciej W. January 7, 2025 at 3:46 PM

Details

Assignee

Reporter

Worked in

Sprint

Affects versions

Priority

Created January 7, 2025 at 3:43 PM
Updated 3 hours ago