A pseudo-bug on this MySQL Provider update: It appears that before querying against the spatial operation, there is an initial query to obtain the SRID for all rows of the table. For large MySQL spatial tables, this initial SRID query is a very expensive operation that ultimately renders it unusable above a certain threshold, perhaps 1 million rows, due to timeout. Unfortunately for use on a dynamic MySQL table, that is not a very large threshold.
One improvement might be to call the GetSRID() on just one row, and assume the rest of the table follows suit. Once past that SRID call, the spatial index in MySQL is very effective at returning relevant results even on a very large dataset. I will add a ticket to the MySQL FDO tracker on this as well. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
