Observed with 2.5 Final ( March 28th, 2008 ) using SQL Server and SelfServicing:
This is a follow up to the issue: "Issue using Relations.ObeyWeakRelations with PrefetchPath.Add" (http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=11903), in which Frans mentioned that the problem with LLBLGen generating incorrect SQL when RelationCollections with ObeyWeakRelations turned on are used with PrefetchPaths could not easily be fixed ....
I understand that the join issue might not be fixable, but the fact that LLBLGen generates bad SQL without any warning is scary. Would it be possible to throw an exception or similar in this situation (where ObeyWeakRelations is set to true on a PrefetchPath call) so that the developer would have some hint about what is wrong? It took me a long time to figure out why my query wasn't getting the correct results, and I'm hoping there's a way for other developers to avoid spending that time. I realize that throwing an Exception when one wasn't thrown before is not likely a change that you'd be willing to make as it might break perfectly fine code, but maybe there's a way to narrow down the issue and only throw an exception if the code is actually about to use an incorrect join?
Thanks,
Wesley