You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Persistence of projections with composite properties #2451
N.B. the issue seems to be related to TemplateSupport.createAndApplyPropertyFilter which gets additionalFields.key1 in the NAME_OF_PROPERTIES_PARAM parameter and tries to compare it with the composite property additionalFields
I've hit this problem as well, composite properties are not saving when using saveAs. Are there any workarounds to save these properties to the database?
Activity
meistermeier commentedon Nov 25, 2021
Thanks for reporting this.
I would link this to #2371 because as far as I understood what is happening, both issues are very close.
surjitbhachu commentedon Dec 3, 2021
I've hit this problem as well, composite properties are not saving when using
saveAs. Are there any workarounds to save these properties to the database?cberes commentedon Jan 28, 2022
@meistermeier Just encountered this problem. We use CompositeProperty with and without a converter, and both scenarios are affected.
michael-simons commentedon Jan 31, 2022
Thanks everyone for reporting this. It will be fixed from 6.1 onwards.
GH-2451 - Apply property filter correctly to composite properties too.
GH-2451 - Apply property filter correctly to composite properties too.
GH-2451 - Polishing.
GH-2371 - Respect `@Property` information in projection.
GH-2371 - Respect `@Property` information in projection.
GH-2371 - Respect `@Property` information in projection.
GH-2451 - Apply property filter correctly to composite properties too.
GH-2451 - Polishing.
GH-2371 - Respect `@Property` information in projection.