Ticket #2642 (new defect)
getFilter() returns filter string with double quotes
|Reported by:||armin||Owned by:||dmorissette|
if the FILTER definition in the map file is placed inside double quotes, the request getFilter() or getFilterString() for a layer object returns the filter string literally, i.e. with the double quotes. The same happens to getExpression() on a class object.
If this is an intended behaviour it should at least be mentioned in the docs to avoid quotes in the map file. The problem arises e.g. when I return the filter expression for a PostGIS layer and apply it again on the layer, it will give an error since the WHERE clause sent to the database includes the double quotes (which is not valid SQL).