<div>Does this look like your left join problem?</div>
<div> </div>
<div><a href="http://trac.osgeo.org/mapguide/ticket/1162" target="_blank">http://trac.osgeo.org/mapguide/ticket/1162</a></div>
<div> </div>
<div>I've asked on the -internals list whether the patch for this has been submitted and will be in the 2.2 release.</div>
<div> </div>
<div>Are you seeing any relevant errors in the MapGuide error log? After you get the error, if you restart the MapGuide service and re-connect, can you still not delete the underlying feature source?</div>
<div> </div>
<div>I don't recall seeing any prior reports of this behaviour, so it's likely that you'll be stuck on 1.1 indefinitely unless you file a Trac ticket that allows a developer to quickly and easily reproduce the problem. It may also be helpful to confirm that this is a generic MapGuide problem and not a Studio problem by going through the process from start to finish using Maestro.</div>
<div> </div>
<div>Notes on how to file a ticket are available here; might want to search first to see if there is anything that looks similar, but I couldn't find any with a quick search:</div>
<div> </div>
<div><a href="http://trac.osgeo.org/mapguide/wiki/SubmitTicket" target="_blank">http://trac.osgeo.org/mapguide/wiki/SubmitTicket</a></div>
<div> </div>
<div>Re: validator, Maestro has the ability to right-click on any resource and validate it and its dependencies. It quickly finds things like layers that have had their feature sources moved out from under them, mismatched coordinate system definitions, etc.</div>
<div> </div>
<div>Jason<br><br></div>
<div class="gmail_quote">On 23 April 2010 07:26, _Jon_ wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br><br>Okay, this is still not right. I started over by manually re-building my<br>repository from scratch. I manually re-created the database connections and<br>
my load procedures, and loaded all of my SDF files into the Library. I went<br>through and I defined the joins on a few of them. However, when I create a<br>layer, the joins are still not working properly. They are behaving like<br>
inner joins, even though they are configured as left outer joins. So, I<br>went back in to the feature source that was giving me problems, tickled a<br>few of the settings, and lo-and behold, it gave me the same error as before<br>
when I try to save! This is not a data migration issue - it has to be<br>something else. It has something to do with the interaction between the<br>layer and the feature resource. I can open any of the sdf files and save<br>
them UNTIL I create a themed layer using that resource. Once I create a<br>layer, the feature source becomes "broken", even if I point the layer to a<br>different feature source. Interestingly, Maestro does not report a problem<br>
with the resource.<br></blockquote></div>