This content has been marked as final. Show 2 replies
When the EVALUATE operator is used as a join predicate, an ORDERED hint may be required to force a nested-loop join with the table storing expressions as the inner table. This is a side-effect from the extensible indexing behavior. Please refer to article "Filter Data Before You Get it" under "Code listing 9" in the May'05 issue of Oracle magazine for exact syntax.
Since the data used for the expression evaluation is from another table, you may want to use a table alias attribute in the attribute set(using EXF$TABLE_ALIAS).
Please let me know if you need additional help.
I'd love to see how you are doing this. I am evaluating the expression filter feature and your approach sounds interesting. I'm trying to figure out how it could be used to match multiple event/attributes on multiple tables.