Create an Extended Feature Class on your *primary* Feature Source that joins to your non-spatial table in your Postgres Feature Source. The resulting Extended Feature Class presents a joined view of the two sets of data.
Only recommended if you're on 2.4, and if joining on a single column/property. Feature Join performance really sucks in previous versions, and buggy too. - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/How-to-connect-the-Postgres-database-table-to-MapGuide-tp4992126p4992291.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
