Are your primary (water_pipeline) and secondary sources (other_table) from the same postgres db?
If so, just make a view that is a join of the two tables and style your layer off of that view (that should appear as a Feature Class). Or alternatively, make an Extended Feature Class in your Feature Source (the one where water_pipeline comes from) that's a joins onto other_table and style your layer off of that Extended Feature Class. First option is the easiest but may produce un-selectable layers when based off of a view. You would use Schema Overrides to fix the identity properties of this view-based Feature Class (see: http://themapguyde.blogspot.com.au/2010/08/using-fdo-schema-overrides.html) The second option uses the Feature Join mechanism in MapGuide, which until MGOS 2.4, was fraught with bugs and terrible performance in the most general cases. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MapGuide-LineRule-Label-Text-Change-in-RunTime-tp5055186p5055197.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
