Hi All, I was wondering if anyone uses this feature (pardon the pun).
When I first started with MapGuide, this was the feature that was of most interest to me as it seemed like an easy way to link spatial data with whatever non-spatial databases we have around. But after many bad experiences with performance, and some really nasty join bugs (mainly http://trac.osgeo.org/mapguide/ticket/502), I've have totally shunned using feature joins, and either resorting to either pre-joining, baking the data and refreshing the dataset at regular intervals, or using a spatially enabled rdbms that does the joins at the dbms level. I've have followed the best practices guide, but is seems every database I have encountered has its own set of quirks that don't play nice with MapGuide. Most of our clients were sold on the feature joins capability (well by my sales colleagues anyway), and it pains me (as an implementer, one to has to deliver) to have to workaround this feature because it fails to perform at a satisfactory level. I'd like to hear other people's experiences with feature joins. Is your experience better/worse? - Jackie -- View this message in context: http://n2.nabble.com/Does-anyone-use-Feature-Joins--tp1646599p1646599.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
