You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/07/18 16:42:04 UTC
[jira] [Commented] (SLING-3773) Drop order by clause in the query
made for VanityPath
[ https://issues.apache.org/jira/browse/SLING-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066398#comment-14066398 ]
Chetan Mehrotra commented on SLING-3773:
----------------------------------------
[~asanso] Can you have a look?
> Drop order by clause in the query made for VanityPath
> -----------------------------------------------------
>
> Key: SLING-3773
> URL: https://issues.apache.org/jira/browse/SLING-3773
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.1.0
> Reporter: Chetan Mehrotra
> Priority: Minor
> Fix For: Resource Resolver 1.1.2
>
>
> Currently Resource Resolver's MapEntries uses following query for loading the VanityPaths
> ====
> SELECT sling:vanityPath, sling:redirect, sling:redirectStatus FROM sling:VanityPath WHERE sling:vanityPath IS NOT NULL ORDER BY sling:vanityOrder DESC
> ====
> It specifies the ORDER By for vanityOrder. However the code later does a custom sorting in MapEntry. So we can possibly drop the order by clause
--
This message was sent by Atlassian JIRA
(v6.2#6252)