Resolving already initialized collection elements leads to assertion error

Description

When running a query that initializes collection element state of an already initialized collection, we get into a special code path which currently wrongly tries to resolve element state of all collection elements at once, though it should only resolve the state for the element of the current row.

This leads to an assertion error because the InitializerData of a nested collection is in the wrong state when resolving the second element.

Activity

Show:
Fixed

Details

Assignee

Reporter

Sprint

Fix versions

Affects versions

Priority

Created August 15, 2024 at 8:53 AM
Updated September 16, 2024 at 9:24 PM
Resolved August 16, 2024 at 11:30 AM