In the meantime, you can shift this logic to a DMI or a server-side script, or a custom whereClause. Moving it to the whereClause is particularly easy:
Code:
<whereClause>$defaultWhereClause AND (type = 'C' OR type = 'G')</whereClause>
<whereClause>$defaultWhereClause AND (type = 'C' OR type = 'G')</whereClause>
new AdvancedCriteria(OperatorId.OR, new Criterion[]{ new Criterion("type", OperatorId.EQUALS, "C"), new Criterion("type", OperatorId.EQUALS, "G") });
<AdvancedCriteria operator="or"> <criteria> <AdvancedCriteria operator="equals" fieldName="type" value="C" /> <AdvancedCriteria operator="equals" fieldName="type" value="G" /> </criteria> </AdvancedCriteria>
<operationBindings> <operationBinding operationId="threatenedFetch" operationType="fetch"> <criteria> <AdvancedCriteria operator="iEquals" fieldName="status" value="Threatened" /> </criteria> </operationBinding> </operationBindings>
<AdvancedCriteria operator="or"> <criteria> <AdvancedCriteria .../> <AdvancedCriteria .../> </criteria> </AdvancedCriteria>
<operationBinding operationType="fetch"> <criteria fieldName="deleted" value="false"/> </operationBinding>
new Criterion("eventtype", OperatorId.EQUALS, new Integer[]{2, 4, 5, 11});
new AdvancedCriteria(OperatorId.OR, new Criterion[]{ new Criterion("eventtype", OperatorId.EQUALS, 2), new Criterion("nodetype", OperatorId.EQUALS, 4) });
Leave a comment: