I could 't repeat this issue with and King.Oracle 0.8.5 provider and MGOS 2.0.2.
Testing http://localhost/mapguide/mapagent/selectfeaturesform.html
with different FDO classes and different filter string like ( OBJECT_ID >= 30919 ) or(  OBJECT_ID >= 30919 AND PARENT_ID= 10 )
i get correct results.

Using "=>" returns FDO exception  "String does not represent a valid filter" so you should use ">="

Simon

Kenneth Skovhede, GEOGRAF A/S wrote:
I was testing the King.Oracle 0.8.5 provider, using the standard form:
http://localhost/mapguide/mapagent/selectfeaturesform.html

Using the previous version (the one included in FDO 3.3.1 / MGOS 2.0.2),
I could not get it to return any feature if I entered a non-trivial filter like:
ID => 0 or ID <= 0
The filter 1=1 seems to work though.

The updated version seems to have trouble if I specify a column.
Specifying no columns seems to revert to the previous behavior.

Is this a known issue or limitiation?


No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.5/1881 - Release Date: 7.1.2009 17:59

  
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Reply via email to