- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我们正在使用 Entity Framework,我们想执行一个简单的 LEFT JOIN。
事实上,这是我们希望在 LINQ (Queryable) 中拥有的 SQL:
SELECT
cbl.ID as ClaimBatchLine_ID
,cbl.PurchasePrice
,c.*
,ic.DueDate
,ic.Reference
FROM ClaimBatchLine cbl
INNER JOIN Claim c ON c.ID = cbl.CLaim_ID
LEFT JOIN InvoiceClaim ic ON ic.ID = c.ID
WHERE cbl.ClaimBatch_ID = @claimBatchId
ORDER BY cbl.ID
OFFSET (@recordsPerPage*@page) ROWS
FETCH NEXT @recordsPerPage ROWS ONLY
我们想出的是:
from cbl in ClaimBatchLines where cbl.ClaimBatch_ID == 1
from c in Claims where c.ID == cbl.Claim_ID
from ic in InvoiceClaims.DefaultIfEmpty() where ic.ID == c.ID
select new {cbl, c, ic.Reference}
这会产生以下 SQL。
SELECT [t0].[ID],
[t0].[ClaimBatch_ID],
[t0].[Claim_ID],
[t0].[PurchasePrice],
[t1].[ID] AS [ID2],
[t1].[ClaimType_ID],
[t1].[Debtor_ID],
[t1].[CustomerContractRevision_ID],
[t1].[Date],
[t1].[CreatedOn],
[t1].[GrossAmount],
[t1].[OpenAmount],
[t1].[IsProcessedByOpenAmountCalculator],
[t1].[RowVersion],
[t2].[Reference] AS [Reference]
FROM [ClaimBatchLine] AS [t0]
CROSS JOIN [Claim] AS [t1]
LEFT OUTER JOIN [InvoiceClaim] AS [t2] ON 1 = 1
WHERE([t2].[ID] = [t1].[ID])
AND ([t1].[ID] = [t0].[Claim_ID])
AND ([t0].[ClaimBatch_ID] = @p0);
它产生相同的结果集。那太好了。但是,如您所见,LEFT OUTER JOIN [InvoiceClaim] AS [t2] ON 1 = 1
并不是我们想要的。我希望它能将其转换为 LEFT JOIN InvoiceClaim ic ON ic.ID = c.ID
。
我们做错了什么吗?或者 LINQ to SQL 只是次优(就性能而言)并且无法理解我们想要什么。
编辑:在 LINQPad 中,这会产生一些不错的查询
from cbl in ClaimBatchLines
join c in Claims on cbl.Claim_ID equals c.ID
join ic in InvoiceClaims on c.ID equals ic.ID into g
from e in g.DefaultIfEmpty()
where cbl.ClaimBatch_ID == 1
select new {cbl, c, e.Reference}
即
-- Region Parameters
DECLARE @p0 INT= 1;
-- EndRegion
SELECT [t0].[ID],
[Columns left out for brevity]
[t2].[Reference] AS [Reference]
FROM [ClaimBatchLine] AS [t0]
INNER JOIN [Claim] AS [t1] ON [t0].[Claim_ID] = [t1].[ID]
LEFT OUTER JOIN [InvoiceClaim] AS [t2] ON [t1].[ID] = [t2].[ID]
WHERE [t0].[ClaimBatch_ID] = @p0;
但是当像这样添加分页功能时:
(from cbl in ClaimBatchLines
join c in Claims on cbl.Claim_ID equals c.ID
join ic in InvoiceClaims on c.ID equals ic.ID into g
from e in g.DefaultIfEmpty()
where cbl.ClaimBatch_ID == 1
select new {cbl, c, e.Reference})
.OrderBy(a => a.cbl.ID)
.Skip(0 * 15000)
.Take(15000)
它产生了这个“怪物”:
-- Region Parameters
DECLARE @p0 INT= 1;
DECLARE @p1 INT= 0;
DECLARE @p2 INT= 15000;
-- EndRegion
SELECT [t4].[ID],
[Columsn left out for brevity...]
FROM
(
SELECT ROW_NUMBER() OVER(ORDER BY [t3].[ID]) AS [ROW_NUMBER],
[Columsn left out for brevity...]
FROM
(
SELECT [t0].[ID],
[Columsn left out for brevity...]
FROM [ClaimBatchLine] AS [t0]
INNER JOIN [Claim] AS [t1] ON [t0].[Claim_ID] = [t1].[ID]
LEFT OUTER JOIN [InvoiceClaim] AS [t2] ON [t1].[ID] = [t2].[ID]
) AS [t3]
WHERE [t3].[ClaimBatch_ID] = @p0
) AS [t4]
WHERE [t4].[ROW_NUMBER] BETWEEN @p1 + 1 AND @p1 + @p2
ORDER BY [t4].[ROW_NUMBER];
更糟的是。当我不是通过 LINQpad 而是在使用 EF 存储库的代码中执行相同的 LINT-To-EF 时,我得到了这个更大的怪物:
SELECT [Project5].[ID] AS [ID],
[Columns left out for brevity...]
[Project5].[Reference] AS [Reference]
FROM
(
SELECT [Extent1].[ID] AS [ID],
[Extent1].[Claim_ID] AS [Claim_ID],
[Extent1].[ClaimBatch_ID] AS [ClaimBatch_ID],
[Extent1].[PurchasePrice] AS [PurchasePrice],
[Join4].[Id1] AS [ID1],
[Join4].[ClaimType_ID] AS [ClaimType_ID],
[Join4].[Debtor_ID] AS [Debtor_ID],
[Join4].[CustomerContractRevision_ID] AS [CustomerContractRevision_ID],
[Join4].[Date] AS [Date],
[Join4].[GrossAmount] AS [GrossAmount],
[Join4].[OpenAmount] AS [OpenAmount],
[Join4].[CreatedOn] AS [CreatedOn],
[Join4].[IsProcessedByOpenAmountCalculator] AS [IsProcessedByOpenAmountCalculator],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN '2X'
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN '2X0X'
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN '2X1X'
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN '2X2X'
ELSE '2X3X'
END AS [C1],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS BIT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN [Join4].[IsAppeared]
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS BIT)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN CAST(NULL AS BIT)
END AS [C2],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS TINYINT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS TINYINT)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN [Join4].[AdjustmentClaimReason_ID]
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN CAST(NULL AS TINYINT)
END AS [C3],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN [Join4].[User_ID]
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN CAST(NULL AS INT)
END AS [C4],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN [Join4].[CostClaimAnnouncement_ID]
END AS [C5],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS DECIMAL(19, 4))
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS DECIMAL(19, 4))
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS DECIMAL(19, 4))
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN [Join4].[DiscountFactor]
END AS [C6],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN [Join4].[DiscountValidTo]
END AS [C7],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN [Join4].[AppliedDiscountAdjustmentClaim_ID]
END AS [C8],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS INT)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN [Join4].[ExpiredDiscountAdjustmentClaim_ID]
END AS [C9],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS VARCHAR(1))
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS VARCHAR(1))
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS VARCHAR(1))
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN CAST(NULL AS VARCHAR(1))
ELSE [Join4].[Reference]
END AS [C10],
CASE
WHEN((NOT(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL)))
AND (NOT(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL)))
AND (NOT(([Join4].[C13] = 1)
AND ([Join4].[C13] IS NOT NULL)))
AND (NOT(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C14] = 1)
AND ([Join4].[C14] IS NOT NULL))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C12] = 1)
AND ([Join4].[C12] IS NOT NULL))
THEN CAST(NULL AS DATETIME2)
WHEN(([Join4].[C11] = 1)
AND ([Join4].[C11] IS NOT NULL))
THEN CAST(NULL AS DATETIME2)
ELSE [Join4].[DueDate]
END AS [C11],
[Extent7].[Reference] AS [Reference]
FROM [dbo].[ClaimBatchLine] AS [Extent1]
INNER JOIN
(
SELECT [Extent2].[Id] AS [Id1],
[Columns left out for brevity...]
FROM [dbo].[Claim] AS [Extent2]
LEFT OUTER JOIN
(
SELECT [Extent3].[Id] AS [Id],
[Extent3].[CostClaimAnnouncement_ID] AS [CostClaimAnnouncement_ID],
[Extent3].[DiscountFactor] AS [DiscountFactor],
[Extent3].[DiscountValidTo] AS [DiscountValidTo],
[Extent3].[AppliedDiscountAdjustmentClaim_ID] AS [AppliedDiscountAdjustmentClaim_ID],
[Extent3].[ExpiredDiscountAdjustmentClaim_ID] AS [ExpiredDiscountAdjustmentClaim_ID],
CAST(1 AS BIT) AS [C1]
FROM [dbo].[CostClaim] AS [Extent3]
) AS [Project1] ON [Extent2].[Id] = [Project1].[Id]
LEFT OUTER JOIN
(
SELECT [Extent4].[Id] AS [Id],
[Extent4].[IsAppeared] AS [IsAppeared],
CAST(1 AS BIT) AS [C1]
FROM [dbo].[InterestClaim] AS [Extent4]
) AS [Project2] ON [Extent2].[Id] = [Project2].[Id]
LEFT OUTER JOIN
(
SELECT [Extent5].[Id] AS [Id],
[Extent5].[AdjustmentClaimReason_ID] AS [AdjustmentClaimReason_ID],
[Extent5].[User_ID] AS [User_ID],
CAST(1 AS BIT) AS [C1]
FROM [dbo].[AdjustmentClaim] AS [Extent5]
) AS [Project3] ON [Extent2].[Id] = [Project3].[Id]
LEFT OUTER JOIN
(
SELECT [Extent6].[Id] AS [Id],
[Extent6].[Reference] AS [Reference],
[Extent6].[DueDate] AS [DueDate],
CAST(1 AS BIT) AS [C1]
FROM [dbo].[InvoiceClaim] AS [Extent6]
) AS [Project4] ON [Extent2].[Id] = [Project4].[Id]
) AS [Join4] ON [Extent1].[Claim_ID] = [Join4].[Id1]
LEFT OUTER JOIN [dbo].[InvoiceClaim] AS [Extent7] ON [Join4].[Id1] = [Extent7].[Id]
WHERE 1 = [Extent1].[ClaimBatch_ID]
) AS [Project5]
ORDER BY [Project5].[ID] ASC
OFFSET 0 ROWS FETCH NEXT 15000 ROWS ONLY;
这到底是怎么回事!在 LINQpad 上抓取最初看起来不错。但是生产代码中的最终查询简直太可怕了!也许这些查询适用于一些简单的应用程序。在更多记录中查询 500k 条记录时,这对我来说不太好。我将坚持使用纯 SQL 表值函数而不是使用 LINQ。真可惜。
最佳答案
试试这个方法:
from cbl in ClaimBatchLines
join c in Claims on c.ID equals cbl.Claim_ID
join ic in InvoiceClaims on ic.ID equals c.ID into g
from e in g.DefaultIfEmpty()
where cbl.ClaimBatch_ID == 1
select new {cbl, c, e.Reference}
有关如何在 linq 中执行左连接的更多信息,请查看此 link
关于c# - 如何使用 EF 编写此 LEFT JOIN 查询,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/42420659/
EF POCO 和 EF Code First 有什么区别? 如果我一开始只使用 POCO,我可以将 EF 与它们一起使用吗? 最佳答案 如果您首先使用 EF 代码,您将拥有 POCO 对象,并且数据
EF POCO 和 EF Code First 有什么区别? 如果我一开始只使用 POCO,我可以将 EF 与它们一起使用吗? 最佳答案 如果您首先使用 EF 代码,您将拥有 POCO 对象,并且数据
我有一个基于 .NET 4.8 和 EF 6.4.4 的项目。我们正在逐步迁移到 .Net Core,但在此过程中我可以创建一个 .NET Core 数据上下文类 EF Core 并将两者指向相同的实
我有以下 Entity Framework 5 代码第一类 public class Airplane { public int Id { get; set; } public int
我正在尝试使用 Entity Framework Core 对现有数据库进行逆向工程.我试着按照指示from Microsoft但我遇到了错误: Unable to find provider ass
当数据库不是由 EF 代码首先创建时,有没有办法检查 DbContext 是否与数据库匹配? 我正在寻找与 Database.CompatibleWithModel 类似的功能但没有元数据。 最佳答案
目前,我正在重构我的上下文方法的测试,以不再需要真正的数据库。我使用 Ef Core。 所以我通读了 Microsoft 文档如何测试上下文方法。我首先找到了 EF6 测试的文档,然后阅读了 EfCo
我正在使用 EF 6 Database.SqlQuery 语句来执行存储过程,并实现错误和事务处理,打开和关闭事务(处理多个记录,如果一个记录有错误,仅回滚此,并提交其他任何内容无错误完成)。 Lis
我首先使用 EF 数据库,因为我喜欢在 SQL Management Studio 中设计我的数据库,坦率地说,让 Visual Studio 直接从数据库创建所有实体非常容易,而无需执行任何代码。
我的项目中有几个迁移文件,由于我对上次迁移进行了手动修改,所以我不想使用“程序包管理器控制台”重新生成它。我只需要添加 1 列。所以在之前的迁移中手动添加了这个(我可以这样做,因为还没有人升级过)。
原文:https://bit.ly/2umidlb 作者:jon p smith 翻译:王亮 声明:我翻译技术文章不是逐句翻译的,而是根据我自己的理解来表述的。其中可能会去除一些本人实在不知道如何组
我们想开始一个新项目,我们决定从一开始就在一些表中使用 Columnstore 索引和聚簇索引,我们如何使用 Code First EF Core 3.1 做到这一点? 最佳答案 您应该将主键更改为非
我在 Entity Framework 6.0 上。这是一个开发问题,而不是生产问题。 我想我有一个相互矛盾的策略。 目前,我设置了 DropCreateDatabaseIfModelChanges
我在 VS 2012 RTM 上,使用 EF 5。我在做代码优先,但由于我只是在开发中,所以试图忽略代码迁移。为了避免它们,我有这一套 Database.SetInitializer(new Drop
我有复杂的审计字段类型 我的复杂类型: [ComplexType] public class AuditData { [Column("CreatorUserId")] public
我已经阅读了很多关于如何在关系中指定外键名称的帖子,没有遇到任何问题。不过,我想知道的是,有没有办法更改主键和关系的命名方式? 例如,您有一个以 UserId 作为主键的 User 表。 EF 代码第
我刚刚安装了新的Entity Framework 4.1 NuGet包,因此根据NuGet指令和this article of Scott Hanselman替换了EFCodeFirst包。 现在,想
我的应用程序基于 .NET 4.0 和 EF 4。我现在正在考虑升级到最新版本。 是否有任何可能对我的申请产生不利影响的重大变化或行为差异? 升级路径有多简单?升级到 EF 5 是否需要任何代码更改或
假设您必须使用 EF Code First 和 POCO 类开发支持多种语言的网站,您将如何对 POCO 类进行建模以支持这种情况? 通过多语言支持,我的意思不仅是拥有例如在一些资源文件中为您的 UI
我首先使用 EF 4.1 代码。鉴于以下类片段: public class Doctor { public virtual ICollection Hospitals { get; set;
我是一名优秀的程序员,十分优秀!