It could be a datastore problem. Is FEATID an identity property?
If it is not, is your feature source pointing to an RDBMS? If so, is the FEATID column indexed? The selection filter could be causing table scans if the column is not PK/indexed, whose slowness would be noticeable on a very large table. - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Client-side-way-to-get-FEATID-s-from-FDO-tp6976596p6976898.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
