在生產場景中,咱們常常用到LINQ運算符進行,如今咱們就來了解下生產場景常常出現幾種複雜查詢運算符。web
藉助LINQ Join運算符,可根據每一個源的鍵選擇器鏈接兩個數據源,並在鍵匹配時生成值的元組。sql
var query = from blog in _context.Set<Blog>() join post in _context.Set<Post>() on blog.BlogId equals post.BlogId select new { blog, post };
SQL:數據庫
SELECT [blog].[BlogId], [blog].[Createtime], [blog].[Updatetime], [blog].[Url], [post].[PostId], [post].[BlogId], [post].[Content], [post].[Title]
FROM [Blog] AS [blog]
INNER JOIN [Post] AS [post] ON [blog].[BlogId] = [post].[BlogId]
SQL Server Profiler:
安全
雖然Left Join不是LINQ運算符,但關係數據庫具備經常使用於查詢的Left Join的概念。LINQ查詢中的特定模式提供與服務器上的LEFT JOIN相同的結果。 服務器
var query = from blog in _context.Set<Blog>() join post in _context.Set<Post>() on blog.BlogId equals post.BlogId into grouping from post in grouping.DefaultIfEmpty() select new { blog, post };
SQL:異步
SELECT [blog].[BlogId], [blog].[Createtime], [blog].[Updatetime], [blog].[Url], [post].[PostId], [post].[BlogId], [post].[Content], [post].[Title]
FROM [Blog] AS [blog]
LEFT JOIN [Post] AS [post] ON [blog].[BlogId] = [post].[BlogId]
SQL Server Profiler:
async
LINQ GroupBy運算符建立IGrouping<TKey, TElement>類型的結果,其中TKey和TElement能夠是任意類型。此外,IGrouping實現了IEnumerable<TElement>,這意味着可在分組後使用任意LINQ運算符來對其進行組合。函數
var query = from blog in _context.Set<Blog>() group blog by blog.Url into g select new { g.Key, Count = g.Count() };
SQL:post
SELECT [blog].[Url] AS [Key], COUNT(*) AS [Count]
FROM [Blog] AS [blog]
GROUP BY [blog].[Url]
SQL Server Profiler:url
分組的聚合運算符出如今Where或OrderBy(或其餘排序方式)LINQ運算符中。它在SQL中將Having子句用於Where子句。
var query = from blog in _context.Set<Blog>() group blog by blog.Url into g where g.Count() > 0 orderby g.Key select new { g.Key, Count = g.Count() };
SQL:
SELECT [blog].[Url] AS [Key], COUNT(*) AS [Count] FROM [Blog] AS [blog] GROUP BY [blog].[Url] HAVING COUNT(*) > 0 ORDER BY [Key]
SQL Server Profiler:
EF Core支持的聚合運算符以下所示:
●Avg
●Count
●LongCount
●Max
●Min
●Sum
1.4SelectMany
藉助LINQ SelectMany運算符,可爲每一個外部元素枚舉集合選擇器,並從每一個數據源生成值的元組。
var query0 = from b in _context.Set<Blog>() from p in _context.Set<Post>() select new { b, p }; var query1 = from b in _context.Set<Blog>() from p in _context.Set<Post>().Where(p => b.BlogId == p.BlogId).DefaultIfEmpty() select new { b, p }; var query2 = from b in _context.Set<Blog>() from p in _context.Set<Post>().Select(p => b.Url + "=>" + p.Title).DefaultIfEmpty() select new { b, p };
SQL:
SELECT [b].[BlogId], [b].[Createtime], [b].[Updatetime], [b].[Url], [p].[PostId], [p].[BlogId], [p].[Content], [p].[Title] FROM [Blog] AS [b] CROSS JOIN [Post] AS [p] SELECT [b].[BlogId], [b].[Createtime], [b].[Updatetime], [b].[Url], [t0].[PostId], [t0].[BlogId], [t0].[Content], [t0].[Title] FROM [Blog] AS [b] CROSS APPLY ( SELECT [t].[PostId], [t].[BlogId], [t].[Content], [t].[Title] FROM ( SELECT NULL AS [empty] ) AS [empty] LEFT JOIN ( SELECT [p].[PostId], [p].[BlogId], [p].[Content], [p].[Title] FROM [Post] AS [p] WHERE [b].[BlogId] = [p].[BlogId] ) AS [t] ON 1 = 1 ) AS [t0] SELECT [b].[BlogId], [b].[Createtime], [b].[Updatetime], [b].[Url], [t0].[c] FROM [Blog] AS [b] CROSS APPLY ( SELECT [t].[c] FROM ( SELECT NULL AS [empty] ) AS [empty] LEFT JOIN ( SELECT ([b].[Url] + N'=>') + [p].[Title] AS [c] FROM [Post] AS [p] ) AS [t] ON 1 = 1 ) AS [t0]
SQL Server Profiler:
好了,這裏就很少寫關於LINQ其餘示例了,若是須要了解的小夥伴們,能夠移步「101個LINQ示例」這裏瞭解。
有一些複雜業務場景,使用LINQ查詢可能會致使SQL查詢效率低下並不適用,那麼這時候就須要到原生SQL查詢了。EF Core爲咱們提供FromSql擴展方法基於原始SQL查詢。 FromSql只能在直接位於DbSet<>上的查詢根上使用。
var blogs = _context.Blog.FromSql("SELECT * FROM dbo.Blog").ToList();
原生SQL查詢可用於執行存儲過程。
var blogs = _context.Blog .FromSql("EXECUTE dbo.GetMostPopularBlogs") .ToList();
向原始SQL查詢引入任何用戶提供的值時,必須注意防範SQL注入攻擊。除了驗證確保此類值不包含無效字符,還要將值與SQL文本參數化處理。
下面的示例經過在SQL查詢字符串中包含形參佔位符並提供額外的實參,將單個形參傳遞到存儲過程。雖然此語法可能看上去像String.Format語法,但提供的值包裝在DbParameter中,且生成的參數名稱插入到指定{0}佔位符的位置。
var url = "http://blogs.msdn.com/webdev"; var blogs = _context.Blog .FromSql("EXECUTE dbo.GetMostPopularBlogForUrl {0}", url) .ToList();
SQL:
exec sp_executesql N'EXECUTE dbo.GetMostPopularBlogForUrl @p0 ',N'@p0 nvarchar(4000)',@p0=N'http://blogs.msdn.com/webdev'
SQL Server Profiler:
還能夠構造DbParameter並將其做爲參數值提供。因爲使用了常規SQL參數佔位符而不是字符串佔位符,所以可安全地使用FromSql:
var urlParams = new SqlParameter("Url", "http://blogs.msdn.com/webdev"); var blogs = _context.Blog .FromSql("EXECUTE dbo.GetMostPopularBlogForUrl @Url", urlParams) .ToList();
SQL:
exec sp_executesql N'EXECUTE dbo.GetMostPopularBlogForUrl @Url ',N'@Url nvarchar(28)',@Url=N'http://blogs.msdn.com/webdev'
SQL Server Profiler:
可以使用LINQ運算符在初始的原始SQL查詢基礎上進行組合。EF Core將其視爲子查詢,並在數據庫中對其進行組合。下面的示例使用原始SQL查詢,該查詢從表值函數 (TVF) 中進行選擇。而後,使用LINQ進行篩選和排序,從而對其進行組合。
var searchTerm = "http://blogs.msdn.com/visualstudio"; var blogs = _context.Blog .FromSql($"SELECT * FROM dbo.Blog") .Where(b => b.Url == searchTerm) .Include(c=>c.Post) .OrderByDescending(b => b.Createtime) .ToList();
SQL:
exec sp_executesql N'SELECT [b].[BlogId], [b].[Createtime], [b].[Updatetime], [b].[Url] FROM ( SELECT * FROM dbo.Blog ) AS [b] WHERE [b].[Url] = @__searchTerm_1 ORDER BY [b].[Createtime] DESC, [b].[BlogId]',N'@__searchTerm_1 nvarchar(4000)',@__searchTerm_1=N'http://blogs.msdn.com/visualstudio' exec sp_executesql N'SELECT [b.Post].[PostId], [b.Post].[BlogId], [b.Post].[Content], [b.Post].[Title] FROM [Post] AS [b.Post] INNER JOIN ( SELECT [b0].[BlogId], [b0].[Createtime] FROM ( SELECT * FROM dbo.Blog ) AS [b0] WHERE [b0].[Url] = @__searchTerm_1 ) AS [t] ON [b.Post].[BlogId] = [t].[BlogId] ORDER BY [t].[Createtime] DESC, [t].[BlogId]',N'@__searchTerm_1 nvarchar(4000)',@__searchTerm_1=N'http://blogs.msdn.com/visualstudio'
SQL Server Profiler:
當在數據庫中執行查詢時,異步查詢可避免阻止線程。異步查詢對於在客戶端應用程序中保持響應式UI很是重要。 異步查詢還能夠增長Web應用程序中的吞吐量,即經過釋放線程,以處理其餘Web應用程序中的請求。
public async Task<IActionResult> Index() { var id1 = Thread.CurrentThread.ManagedThreadId.ToString(); var blogs = await _context.Blog.ToListAsync(); var id2 = Thread.CurrentThread.ManagedThreadId.ToString(); return View(blogs); }
當咱們運行以上代碼時候,經過在關鍵字await上下文加入兩段獲取線程ID代碼,咱們會看到以下結果:
看到兩段線程代碼輸出ID結果沒有?從上圖能夠觀察到,當咱們在進入某個視圖或者方法時候,執行到await某一個方法,當前線程不會一直等待下去,會立馬回收到線程池,供其餘地方調用!當該await方法返回數據時候,才從線程池調用空閒線程執行await方法下文餘下的步驟。因此UI界面纔不會進入假死狀態。
參考文獻:
複雜查詢運算符
原生SQL查詢
異步查詢