[ 
https://issues.apache.org/jira/browse/SYNCOPE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039093#comment-17039093
 ] 

ASF subversion and git services commented on SYNCOPE-1502:
----------------------------------------------------------

Commit 2d28f32878426e580d53d4545ce404fb72cf55b3 in syncope's branch 
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2d28f32 ]

[SYNCOPE-1502] Bring back actual result sorting


> Find Anys using FIQL: SQL improvements
> --------------------------------------
>
>                 Key: SYNCOPE-1502
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1502
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.1.5
>            Reporter: Dmitriy B.
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.1.6, 3.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> PR contains improvements when Anys are searched using FIQL queries:
> The resulted SQL query that finds any_to_keys can have a huge list with OR 
> clauses for effective realms. This can be replaced to the IN clause.
> {code:sql}
> SELECT u.any_id,sv.username FROM (SELECT DISTINCT any_id FROM user_search 
> WHERE (realm_id=? AND any_id IN ( SELECT DISTINCT any_id FROM user_search 
> WHERE lastChangeDate<=?))) u,user_search sv WHERE u.any_id=sv.any_id AND 
> u.any_id IN (SELECT any_id FROM user_search WHERE realm_id IN (SELECT id AS 
> realm_id FROM Realm WHERE id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR 
> id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? 
> OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR id=? OR 
> id=? OR id=? OR id=? OR id=?)) ORDER BY sv.username ASC
> {code}
> When anys are searched by keys a lot of single sql queries are executed. This 
> can be improved using single SQL query with In clause.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to