That does indeed look like it might be related. I'm not exactly sure what the GWS query engine is or when it is involved in querying features, but if I am interpreting this correctly, this would mean that ANY left outer join would behave like an inner join. The severity is marked as "trivial", which leaves me confused - I would expect a left outer join to be rather common and necessary. I didn't think I was doing something all that special. In fact, this was the only join type available back in 1.1. I guess I will have to submit a defect just to be sure.
I think you are correct that the surrounding behavior of errors might be Studio issues. The problem only appears after I refresh the preview of the joined layer and restarting the service makes the errors stop. Displaying the preview via Maestro does not cause the feature source to break, but Maestro shows the preview in a slightly different way. Thank you for your advice and suggestions! Jon -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Join-Problem-tp4946935p4952527.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
