-
I have a database with some pointers. But when using |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
This is expected behavior and one level deep is listed in the documentation. The server currently only allows 1-deep. You can see my comments and discussion about this with relevant links here: parse-community#359 (comment) If you want to go multiple layers deep, i.e 3-deep, and you know where you want to stop, use: // Each of these are a Parse Pointer
.include("1deep.2deep.3deep", "field2", etc.) Note, if the server ever enables this type of feature, there's a potential for infinite loops as the client SDK's are what has protected against cycles historically, not the server. All clients have their own specific designs for detecting cycles (for example, the Swift SDK is nothing like the others), so if a client SDK introduced a cycle on your server via a bug that has never been patched or your app allows data to be uploaded directly through REST or GraphQL and skipped a cycle check, you are in trouble. In addition, I can see a number of different nightmares introduced by this feature as well... I recommend sticking with specific queries (like my example above) and when needed querying again if you want your system to remain efficient. |
Beta Was this translation helpful? Give feedback.
This is expected behavior and one level deep is listed in the documentation. The server currently only allows 1-deep. You can see my comments and discussion about this with relevant links here: parse-community#359 (comment)
If you want to go multiple layers deep, i.e 3-deep, and you know where you want to stop, use:
Note, if the server ever enables this type of feature, there's a potential for infinite loops as the client SDK's are what has protected against cycles historically, not the server. All clients have their own specific designs for detecting cycles (for example, the Swift SDK is nothing like the o…