<div>Bruce has confirmed that the patch attached to that ticket was applied, and closed the ticket. I believe that it was after 2.1 was released though.</div><div><br></div>If you feel like living on the edge, there is a pre-alpha installer for 2.2 available here:<div>
<br></div><div><a href="http://download.osgeo.org/mapguide/testing/">http://download.osgeo.org/mapguide/testing/</a></div><div><br></div><div>MapGuideOpenSource-2.2.0.4686-Test.exe</div><div><br></div><div>Not guaranteed to work or anything, but if it does it would allow you to verify whether the fix to the original ticket solves the join problem you're seeing.</div>
<div><br></div><div>Being a MapGuide 6.5 customer, I started using joins with early MapGuide OS versions, had tonnes of headaches from stability and performance perspectives, and ended up using FME to write everything to SDF on a nightly basis instead and haven't looked back. I wouldn't be surprised if many other early adopter production MapGuide sites ran into the same problems and abandoned joins. I'm not convinced that joins are fully mature yet, even at 2.2, but they should be considerably better.</div>
<div><br></div><div>Jason</div><div><br></div><div><br><div class="gmail_quote">On 23 April 2010 13:23, _Jon_ wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
That does indeed look like it might be related. I'm not exactly sure what<br>
the GWS query engine is or when it is involved in querying features, but if<br>
I am interpreting this correctly, this would mean that ANY left outer join<br>
would behave like an inner join. The severity is marked as "trivial", which<br>
leaves me confused - I would expect a left outer join to be rather common<br>
and necessary. I didn't think I was doing something all that special. In<br>
fact, this was the only join type available back in 1.1. I guess I will<br>
have to submit a defect just to be sure.<br>
<br>
I think you are correct that the surrounding behavior of errors might be<br>
Studio issues. The problem only appears after I refresh the preview of the<br>
joined layer and restarting the service makes the errors stop. Displaying<br>
the preview via Maestro does not cause the feature source to break, but<br>
Maestro shows the preview in a slightly different way.<br><br></blockquote></div></div>