The PostGIS support underwent major changes recently so I'd suspect this
is specific
to that work. Perhaps there are character padding affecting things?
Steve
>>> Pål Kristensen <[EMAIL PROTECTED]> 11/21/08 8:36 AM >>>
Hi!
I've compiled 5.3-dev from trunk yesterday and got some trouble with
some
mapfiles that works well on 5.2. The problem is that the EXPRESSION
parameter in the CALSS object does not work with direct string
comparison.
Her are some examples:
Does NOT work: (This is the original layer definition from the 5.2
mapfile)
LAYER
...
CLASSITEM "maxhoyde"
...
CLASS
NAME "test"
EXPRESSION "600"
...
END
END
Using RegEx instead WORKS:
LAYER
...
CLASSITEM "maxhoyde"
...
CLASS
NAME "test"
EXPRESSION /600/
...
END
END
Using logical expression WORKS:
LAYER
...
#CLASSITEM "maxhoyde"
...
CLASS
NAME "test"
EXPRESSION ([makshoyde] == 600)
...
END
END
The data is stored in PostgreSQL (PostGIS), and the actual field type is
character(5). Anyone have a clue about what is causing this strange
behavior.
Regards,
Pål Kristensen
--
View this message in context:
http://www.nabble.com/CLASSITEM-and-EXPRESSION-issue-in-trunk--tp20622309p20622309.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
