[mapguide-dev] Enhanced Join Support RFC

[Jason Birch]

Understood.  Like Bob said, it's my job to push :)
 
As to the SDF joins... I was just being fuzzy.  It seems to work, though
Studio doesn't appear to be able to detect the geometry type of the
joined table when selecting its geometry column for representation.  No
idea if this is a MapGuide issue or a Studio issue
 
Jason

________________________________

From: Ronnie Louie [mailto:ronnie.louie at autodesk.com] 
Sent: Wednesday, November 08, 2006 09:38
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] Enhanced Join Support RFC



Hi Jason,

 

Thanks for your comments.  Your suggestions for handling 1:many are duly
noted, however it is not proposed as part of this RFC.  As Bob mentioned
earlier in a previous email, the join functionality is implemented via a
Join component which is also shared with another commercially available
product.  Changes were discussed to support "associations" of a primary
feature record to a set of secondary records, but ultimately did not
make it into that product's release cycle.  I can only speculate that
this support may be part of a future release.  As a result, MapGuide
will be restricted, for now, to the "lazy join" result for the 1:many
case.

 

As for your question on the SDF joins, it should be possible to join
secondary table to a primary table in the same SDF or different SDF
file.  I haven't personally tested this, but if you've got SDFs with
multiple tables, you should be able to see a list of all the available
feature classes in the Studio Join UI for which you can use to define
you join.

 

Ronnie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-internals/attachments/20061108/64529e06/attachment.html