Community
Participate
Working Groups
Build Identifier: When reverse-traversing an EReference using query2, the index information is not used, leading to no performance improvement although the information necessary already seems to be contained in the index. Reproducible: Always Steps to Reproduce: 1. Create a large model with many Resources with cross-references 2. Execute a query2 query looking for objects referencing a specific object through a particular EReference
Hi Axel, As mentioned in the mail earlier, We had tried 2 scenarios related to this issue, where we could not find the issue. 1. An eReference query, where I provide a source/target object and try to find the other eobjects which refer the source. Here, index is being used and depending on source/target, outgoing/incoming links table is looked into, to find the references. 2.Executing a query2 query, trying to get eobjects referencing a particular eobject though eReference, which does not have the eOpposite set. Here too, internally an eReference query is being created with the target eobject, and the usage of index is the same as in case 1. In both the above cases, we see that index is being used as expected to find the references. I suppose this is not a bug and hence will change its status to closed. Please re-open this issue in case you find it still exists. Thanks & Regards, Manasa
As discussed closing the issue.
