|   | 78 | In this case, we defined a search that does the following: | 
          
          
            |   | 79 | * It searches for objects that are the latest versions of their version tree. Branches and older versions are ignored. | 
          
          
            |   | 80 | * Both of the following criteria must be fulfilled because of the //AND// operator: | 
          
          
            |   | 81 |  * The object must have the object type //DITA topic//. | 
          
          
            |   | 82 |  * The object must NOT have ANY value of //parent.relations.child_content//. This means, that there may be no objects that refer to the content of the objects returned by the search. | 
          
          
            |   | 83 |  | 
          
          
            |   | 84 | By combining the structures and functions described in this article, you can create searches of significant complexity. | 
          
          
            |   | 85 |  | 
          
          
            |   | 86 | > **NOTE:** A very complex search is not slower than a very simple search. The index performance scales with the number of results, not with the number of terms it evaluates. One exception is that you should avoid the //contains// comparison operator if possible. Compared with other operators like //equals// or //starts with// it is significantly slower due to the index concept. | 
          
          
            |   | 87 |  |