> > In above case wondering if we could do this > > Min(a) = 2 is the condition, generate condition *"a <= 2"* and push it > down as scan key. Since pushed down condition is lossy one for us ( it > gives values < 2), finally do a recheck of *"Min(a) = 2"*. > > For Max(a) = 2 we can have *"a >=2"*, >
After replying, I was thinking along these lines too. I can't see any reason why it wouldn't work. The same would apply for HAVING clauses on min/max aggregations as well. For min, you should be able to pre-filter =, < , and <=. In all cases the pre-filter would be <=. For max it would be =, > , >= becoming >=. - Doug Doole Salesforce