[fdo-trac] #802: mUseNesting is not right

[FDO]

#802: mUseNesting is not right
-----------------------------+----------------------------------------------
   Reporter:  ChristineBao   |       Owner:  thomasknoell
       Type:  defect         |      Status:  new         
   Priority:  critical       |   Milestone:  3.7.0       
  Component:  ODBC Provider  |     Version:  3.7.0       
   Severity:  2              |    Keywords:              
External_id:  1403527.01     |  
-----------------------------+----------------------------------------------

Comment(by ChristineBao):

 Brent brought a good question about Fix#802_2. It cannot work for:
 COLOR = 0 or (COLOR = 652 or FEATID = 21587) and (FEATID = 20931 or COLOR
 = 256)


 Thanks Brent.

 So I figure out the new rule is: if found a OR operator, check if AND
 operator has already been found -- this is because the process runs from
 root operator to child operator, if AND is found first, and then OR, it
 should add "()" around.
 Please review the new fixing:
 http://trac.osgeo.org/fdo/attachment/ticket/802/Fix%23802_3.patch.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/802#comment:11>
FDO <http://fdo.osgeo.org/>
Feature Data Objects