首先 - Take 错误的一些推理。
如果您只是采取,则查询翻译器只使用顶部。如果加入子集合破坏了基数,Top10 将不会给出正确答案。所以查询翻译器不会加入子集合(而是为子集合请求)。
如果您Skip and Take,那么查询翻译器会在父行上使用一些 RowNumber 逻辑...这些行号让它占用 10 个父行,即使每个父行确实有 50 条记录父母有 5 个孩子。
如果您Skip(0) 和Take,则Skip 会被翻译器作为非操作删除-就像您从未说过Skip。
这将是一个艰难的概念飞跃,从您所在的位置(调用 Skip and Take)到“简单的解决方法”。我们需要做的是强制翻译发生在翻译器无法将 Skip(0) 作为非操作删除的地方。我们需要调用 Skip,并在稍后提供跳过的号码。
DataClasses1DataContext myDC = new DataClasses1DataContext();
//setting up log so we can see what's going on
myDC.Log = Console.Out;
//hierarchical query - not important
var query = myDC.Options.Select(option => new{
ID = option.ParentID,
Others = myDC.Options.Select(option2 => new{
ID = option2.ParentID
})
});
//request translation of the query! Important!
var compQuery = System.Data.Linq.CompiledQuery
.Compile<DataClasses1DataContext, int, int, System.Collections.IEnumerable>
( (dc, skip, take) => query.Skip(skip).Take(take) );
//now run the query and specify that 0 rows are to be skipped.
compQuery.Invoke(myDC, 0, 10);
这会产生以下查询:
SELECT [t1].[ParentID], [t2].[ParentID] AS [ParentID2], (
SELECT COUNT(*)
FROM [dbo].[Option] AS [t3]
) AS [value]
FROM (
SELECT ROW_NUMBER() OVER (ORDER BY [t0].[ID]) AS [ROW_NUMBER], [t0].[ParentID]
FROM [dbo].[Option] AS [t0]
) AS [t1]
LEFT OUTER JOIN [dbo].[Option] AS [t2] ON 1=1
WHERE [t1].[ROW_NUMBER] BETWEEN @p0 + 1 AND @p1 + @p2
ORDER BY [t1].[ROW_NUMBER], [t2].[ID]
-- @p0: Input Int (Size = 0; Prec = 0; Scale = 0) [0]
-- @p1: Input Int (Size = 0; Prec = 0; Scale = 0) [0]
-- @p2: Input Int (Size = 0; Prec = 0; Scale = 0) [10]
-- Context: SqlProvider(Sql2005) Model: AttributedMetaModel Build: 3.5.30729.1
这就是我们获胜的地方!
WHERE [t1].[ROW_NUMBER] BETWEEN @p0 + 1 AND @p1 + @p2