Posted by Garry Shutler in LINQ
Today I had a problem whereby I had created an association but when the data for my object was retrieved it was joining the tables through a left outer join.
As these joins were non-nullable I wanted to make them perform an inner join to take advantage of the greater performance. In order to do this you need to set the ForeignKey attribute to "true" and CanBeNull to "false". The omission or reversal of either of these attributes will mean LINQ to SQL will assume that the parent object may not exist and will instead perform a left outer join
This will mean you end up with a XML mapping such as:
Of course you also need to create a DataLoadOption so that the parent object gets retrieved along with the child (eagerly):
var options = new DataLoadOptions();
options.LoadWith<Job>(j => j.Project);
context.LoadOptions = options;