I an attempting to construct a query against the estimate archetype.  My question relates to nested constraints.

My initial constraint is simple.

 String[] statusConstraints = {EstimateActStatus.IN_PROGRESS, EstimateActStatus.COMPLETED, EstimateActStatus.POSTED};
  setStatuses(statusConstraints);
  setDefaultSortConstraint(DEFAULT_SORT);
  setConstraints(or(isNull("endTime"), gt("endTime", new Date())));

This issues a normal set of values which can subsequently be filtered by status of complete, in progress or posted.  Mind you the status search field displays all the values but due to the status constraint the query will never display cancelled estimates.

I wish to filter the resultset by either estimate id or customer name.  So I added a searchfield to the workspace layout and utilized the returned value as:

String searchText = getWildcardedText(this.getSearchField());
if(searchText != null){
     AndConstraint idConstraint = and(eq("id",searchText),getConstraints());
     AndConstraint nameConstraint = and(eq("customer",searchText),getConstraints());
     setConstraints(or(idConstraint,nameConstraint));
            }

Unfortunately this produces the an empty result set and the error: Failed to execute query: {0}.

I assume this is because nesting constraints do not behave as sql nesting might do.

ie I expect that it would parse as 

((id="*seachText*") and ((date notNull) or (date() !> endDate))) or ((name=*searchText*) and (date notNull) or (date() !> endDate)))

My createResultSet override only fails when something is written in the searchField so I can only assume its the contraint changes that are causing the error.

Any tips?