Hi,

Is there any way to use DISTINCT in the sql statement generated using FetchProjection method instead of filtering the results after retrieving from database. I am using version 2.0

One of the parameters on the FetchProject method with be an "AllowDuplicates", which will emit a DISTINCT into the query when possible, if set to false.

Matt

MTrinder wrote:

One of the parameters on the FetchProject method with be an "AllowDuplicates", which will emit a DISTINCT into the query when possible, if set to false.

Matt

Thanks for the reply.

I tested by setting this parameter to false and "AllowDuplicates" parameter is not adding DISTINCT to the SQL statement instead of that this is filtering the results after fetching. This is creating a problem for me in paging. So I am looking for if there's any option to add DISTINCT to the SQL statement

There are various reasons why DISTINCT cannot sometime be emitted into the SQL - are you querying any text/memo/blob fields etc...?

Matt

MTrinder wrote:

There are various reasons why DISTINCT cannot sometime be emitted into the SQL - are you querying any text/memo/blob fields etc...?

Matt

No. It's sql statement to read from a View. The view is a UNION of 3 sql statements. Is it because of that?

Please show us how your projectors look like, and the snippet to fetch. The framework can't emit TOP if you have joins in the query, which means duplicates can occur, so it has to filter on the client, as it can't emit DISTINCT. This shouldn't lead to timeouts in all cases, as it simply reads till it has read the # of items to read.