Bug 1123965

Summary: refactor with_taxonomy_scope to optimize SQL
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: ProvisioningAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.4   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/4329
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-28 18:23:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Helms 2014-07-28 18:17:41 UTC 
per Marek's comment on PR #1105

so we find all records within specific location, the find the same for specific organization and then combine these ids which we use in third query? sounds like work for SQL instead of ruby? I understand it's not that easy using ancestry but this does not feel right to me, what do others think?
Comment 1 Eric Helms 2014-07-28 18:17:42 UTC 
Created from redmine issue http://projects.theforeman.org/issues/4329