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
Not sure if this is considered a bug or maybe a documentation update.
I can successfully filter on a.b.c=='some value'.
where a is a manytoOne from the root to 'a' and 'b' is a manytoOne from a to b like this:
`
public class Root{ @manytoone(optional = false, fetch = FetchType.LAZY)
private A a;
}
public class A{ @manytoone(optional = false, fetch = FetchType.LAZY)
private B b;
}
public class B{
private int C;
}
`
When I put that in a property map however I get the following exception: Unknown property: c from entity A
when the key of the property matches (part of) the property path. In my case I defined it as put('b', 'a.b.c')
If I change that to something like: put('myProperty', 'a.b.c')
it works just fine.
I was under the impression that the key part could be any string.
The text was updated successfully, but these errors were encountered:
basven
changed the title
Property map nested association throws exception
Property map nested association throws exception when key matches part of the property path.
Oct 24, 2023
Not sure if this is considered a bug or maybe a documentation update.
I can successfully filter on a.b.c=='some value'.
where a is a manytoOne from the root to 'a' and 'b' is a manytoOne from a to b like this:
`
public class Root{
@manytoone(optional = false, fetch = FetchType.LAZY)
private A a;
}
public class A{
@manytoone(optional = false, fetch = FetchType.LAZY)
private B b;
}
public class B{
private int C;
}
`
When I put that in a property map however I get the following exception:
Unknown property: c from entity A
when the key of the property matches (part of) the property path. In my case I defined it as
put('b', 'a.b.c')
If I change that to something like:
put('myProperty', 'a.b.c')
it works just fine.
I was under the impression that the key part could be any string.
The text was updated successfully, but these errors were encountered: