doing it in the database is the recommended approach, it scales and performs far better than any other approach
plus you have the opportunity to tune a database view using indexes etc On Thu, Aug 16, 2012 at 2:54 PM, Jamo <[email protected]> wrote: > So we have two tables one with say geometry and an id and one with an id and > attributes...? > > I have a similar setup here but I'm affraid the only way to accomplish the > task is to join them either at the DB end or at mapguide. > > I join them at the DB so whenever a change is made it triggers to modify the > combined table so then you maintain the spatial data and the external data > is simply appended when it changes. > > I have used this to join our cadastre (Spatial Data) to our Land Management > System (Attribute Data). > > Hope that helps > > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/Thematic-maps-on-Non-Spatial-Data-tp4994300p4995525.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 -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
