void DocumentSourceProject::manageDependencies(
const intrusive_ptr<DependencyTracker> &pTracker) {
/*
Look at all the products (inclusions and computed fields) of this
projection. For each one that is a dependency, remove it from the
list of dependencies, because this product will satisfy that
dependency.
*/
DependencyRemover dependencyRemover(pTracker);
pEO->emitPaths(&dependencyRemover);
/*
Look at the exclusions of this projection. If any of them are
dependencies, inform the user (error/usassert) that the dependency
can't be satisfied.
Note we need to do this after the product examination above because
it is possible for there to be an exclusion field name that matches
a new computed product field name. The latter would satisfy the
dependency.
*/
DependencyChecker dependencyChecker(pTracker, this);
pEO->emitPaths(&dependencyChecker);
/*
Look at the products of this projection. For inclusions, add the
field names to the list of dependencies. For computed expressions,
add their dependencies to the list of dependencies.
*/
pEO->addDependencies(pTracker, this);
}
void DocumentSourceProject::manageDependencies(
const intrusive_ptr<DependencyTracker> &pTracker) {
/*
If the $project is in "inclusionary mode," then it produces
a closed result set
*/
if (!pEO->isExclusionMode())
pTracker->setClosedSet();
/*
Look at all the products (inclusions and computed fields) of this
projection. For each one that is currently a dependency, remove it
from the list of dependencies, because this product will satisfy that
dependency.
First look at the included paths
*/
ExpressionObject::DependencyRemover dependencyRemover(pTracker);
pEO->emitPaths(&dependencyRemover);
/* the computed expressions are also products */
intrusive_ptr<Iterator<string> > pFieldIter(pEO->getFieldIterator());
while(pFieldIter->hasNext()) {
string fieldName(pFieldIter->next());
FieldPath fieldPath(fieldName);
pTracker->removeDependency(fieldPath);
}
/*
Look at the exclusions of this projection. If any of them are
dependencies, inform the user (error/usassert) that the dependency
can't be satisfied.
Note we need to do this after the product examination above because
it is possible for there to be an exclusion field name that matches
a new computed product field name. The latter would satisfy the
dependency.
*/
DependencyChecker dependencyChecker(pTracker, this);
pEO->emitPaths(&dependencyChecker);
/*
Look at the products of this projection. For inclusions, add the
field names to the list of dependencies. For computed expressions,
add their dependencies to the list of dependencies.
*/
pEO->addDependencies(pTracker, this);
}
