Probably a result of some of the PostGIS driver work that was done for 5.4. A bug would be wise I think. Make sure to assign to the PostGIS component.
Steve >>> On 3/12/2009 at 4:00 PM, in message <[email protected]>, Gregor >>> at HostGIS <[email protected]> wrote: > Jennifer Shanks wrote: >> FILTER "(access_cod = 'Restricted Access' or access_cod = 'Open Access')" > > I suggested the parens as disambiguation, when I saw this in > PostgreSQL's query log. > > WHERE code = 'Restricted' or code = 'Open' and gid = 12345 > > As such, her own FILTER clause seems just fine but when combined with > MapServer's behind-the-work an ambiguous clause was generated. Would it > be appropriate to open a ticket on this, to have the PostGIS driver > automatically place the statement in parens in order to prevent such > "MapServer-induced ambiguity" ? _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
