anchor.diff:      buildAST = true;
       defaultErrorHandler = false;
   }
  +
  +// NOTE - BIOSEG_CONSTRAINT and INT4RANGE_CONSTRAINT are commented out throughout this file.
  +// BIOSEG_CONSTRAINT was being parsed here but isn't included in the java classes that represent
  +// sql queries. The BIOSEG_CONSTRAINT was parsed then dropped from the query, which could lead to
  +// bad matches to precomputed tables. Parsing has been removed here, which means and query that
  +// includes range constraints won't be optimised but bad precompute matches won't occur.
   
   tokens {
       SQL_STATEMENT;
  
positive.code:             | (inlist_constraint)=> inlist_constraint
              | constraint
              | not_constraint
  //            | bioseg_constraint
  //            | int4range_constraint
      ;
  
negative.code:     SUBQUERY_CONSTRAINT;
      INLIST_CONSTRAINT;
      ORDER_DESC;
  //    BIOSEG_CONSTRAINT;    see NOTE above
  //    INT4RANGE_CONSTRAINT;
  }
  
  
  start_rule: sql ;
  
  