Im using the method below to select distinct a typed list, but distinct is not being emitted during the SQL trace. For example, I'm using the same method with different typed lists and I am getting a select distinct emitted (SELECT DISTINCT TOP 10000). But in the case below all I'm getting is (SELECT TOP 10000).

public static CustomMessageListTypedList GetCustomMessageBySubProductName(string SubProductName) { CustomMessageListTypedList customMessageList = new CustomMessageListTypedList();

        IPredicateExpression selectFilter = new PredicateExpression();
        selectFilter.Add(PredicateFactory.CompareValue(IssueTrackerSubProductsFieldIndex.SubProductName, ComparisonOperator.Equal, SubProductName));

        customMessageList.Fill(10000, null, false, selectFilter);

        return customMessageList;

}

Do you have any binary/blob fields in the resultSet, like image, text fields?

Ha, you guessed it, I got the answer from our senior developer right as your post came in. It's a text field so it can't be done.

I was thinking that the DISTICT would still be emitted but throw an exception at runtime.

I was thinking that the DISTICT would still be emitted but throw an exception at runtime

LLBLGen Pro is smart enough

Walaa wrote:

I was thinking that the DISTICT would still be emitted but throw an exception at runtime

LLBLGen Pro is smart enough

Indeed (Unlike Linq to sql )

If it can't use distinct, it switches to client-side filtering of duplicates, so it will fetch objects only if they're not in the cached set of entities already in the set fetched/collection.