You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bd...@apache.org on 2017/09/26 11:10:51 UTC

[2/2] sling-site git commit: Fix Sling Query table

Fix Sling Query table


Project: http://git-wip-us.apache.org/repos/asf/sling-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/sling-site/commit/e0d86f78
Tree: http://git-wip-us.apache.org/repos/asf/sling-site/tree/e0d86f78
Diff: http://git-wip-us.apache.org/repos/asf/sling-site/diff/e0d86f78

Branch: refs/heads/master
Commit: e0d86f78c3d8b4b06eadec8503d5b352f3da8f0f
Parents: bdde83a
Author: Bertrand Delacretaz <bd...@apache.org>
Authored: Tue Sep 26 13:10:37 2017 +0200
Committer: Bertrand Delacretaz <bd...@apache.org>
Committed: Tue Sep 26 13:10:37 2017 +0200

----------------------------------------------------------------------
 .../content/documentation/bundles/sling-query/vs-jcr.md   | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/sling-site/blob/e0d86f78/src/main/jbake/content/documentation/bundles/sling-query/vs-jcr.md
----------------------------------------------------------------------
diff --git a/src/main/jbake/content/documentation/bundles/sling-query/vs-jcr.md b/src/main/jbake/content/documentation/bundles/sling-query/vs-jcr.md
index 6d4e0fc..8d439d1 100644
--- a/src/main/jbake/content/documentation/bundles/sling-query/vs-jcr.md
+++ b/src/main/jbake/content/documentation/bundles/sling-query/vs-jcr.md
@@ -11,10 +11,10 @@ As a rule of thumb - if you have a complex Java loop reading resource children o
 
 | Description                                           | JCR query | SlingQuery |
 | ------------------------------------------------------|-----------|------------|
-| You have a complex logic using Sling Resource API     | -         | Yes!       |
-| You want to find resource ancestor                    | -         | Yes!       |
-| You want to find all descendants with given attribute | Yes!      | -          |
-| You want to find all descendants of given type        | Yes!      | -          |
-| You'd like to get ordered results                     | Yes!      | -          |
+| You have a complex logic using Sling Resource API     | (-)       | Yes!       |
+| You want to find resource ancestor                    | (-)       | Yes!       |
+| You want to find all descendants with given attribute | Yes!      | (-)        |
+| You want to find all descendants of given type        | Yes!      | (-)        |
+| You'd like to get ordered results                     | Yes!      | (-)        |
 
 [1] - Actually, the `find()` operation uses QUERY strategy by default, which means that the selector string is transformed to a SQL2 query. However, the transformation process is very naïve and simply skips all conditions that can't be easily transformed to SQL2 (eg. selector `[jcr:content/jcr:title=some title]` won't be transformed as it contains some subresource reference). The result of this query is then filtere manually. See [searchStrategy](methods.html#searchstrategystrategy) for more details.