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 all keypaths used in queries has to be specified in full and has to match the schema to not give an error. This is a problem for enabling search on dynamic properties, and in general makes it hard to adapt queries to less predictable scenarios.
NSPredicates solves this by allowing you to substitute keypaths using the %K identifier:
"%K == %@"
pass a string variable to %K, it will be represented as a keypath, then check if it’s value is equal to value passed in
We should allow the same in RQL. Since our substitution syntax is slightly different (using $<pos> instead of %@) we might want to use a simple annotation to signify that this substitution should be interpreted as a keypath (like $<pos>k).
Currently all keypaths used in queries has to be specified in full and has to match the schema to not give an error. This is a problem for enabling search on dynamic properties, and in general makes it hard to adapt queries to less predictable scenarios.
NSPredicates solves this by allowing you to substitute keypaths using the
%K
identifier:We should allow the same in RQL. Since our substitution syntax is slightly different (using
$<pos>
instead of%@
) we might want to use a simple annotation to signify that this substitution should be interpreted as a keypath (like$<pos>k
).Part of #2978
The text was updated successfully, but these errors were encountered: