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
Currently we only allow simple or treat mappings, see #327
It would be nice though to also support COALESCE and CASE WHEN. All mappings in a subview are then prefixed with that expression. COALESCE is transformed to CASE WHEN in such a case. For e.g. myAttribute we render CASE WHEN parent IS NOT NULL THEN parent.myAttribute ELSE other.myAttribute END. This only works for basic mappings though i.e. it's not possible to fetch entities this way and this should be validated.
I also don't think that that a @Limit mapping can work for something like that. This shouldn't be an issue though, because the individual parts can define a limit by declaring them as @EntityViewRoot.
The text was updated successfully, but these errors were encountered:
Currently we only allow simple or treat mappings, see #327
It would be nice though to also support
COALESCE
andCASE WHEN
. All mappings in a subview are then prefixed with that expression.COALESCE
is transformed toCASE WHEN
in such a case. For e.g.myAttribute
we renderCASE WHEN parent IS NOT NULL THEN parent.myAttribute ELSE other.myAttribute END
. This only works for basic mappings though i.e. it's not possible to fetch entities this way and this should be validated.I also don't think that that a
@Limit
mapping can work for something like that. This shouldn't be an issue though, because the individual parts can define a limit by declaring them as@EntityViewRoot
.The text was updated successfully, but these errors were encountered: