You need to try with a spatial filter specified like I suggested. I'm not disputing the FDO provider's ability to read geometry data out of MySQL (as your screenshots have proven), I'm disputing the FDO provider's ability to properly translate a FDO spatial filter to a SQL WHERE clause in MySQL due to the aforementioned long/lat <-> lat/long orientation change or some other breaking change introduced with MySQL 8.0.
When you're looking at a map in MapGuide, it is always sending queries *with spatial filters* even if you're looking at "everything". - Jackie -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
