LINQ: When to use SingleOrDefault vs. FirstOrDefault() with filtering criteria

LINQ: When to use SingleOrDefault vs. FirstOrDefault() with filtering criteria

问题

 

 

 

回答1

If your result set returns 0 records:

  • SingleOrDefault returns the default value for the type (e.g. default for int is 0)
  • FirstOrDefault returns the default value for the type

If you result set returns 1 record:

  • SingleOrDefault returns that record
  • FirstOrDefault returns that record

If your result set returns many records:

  • SingleOrDefault throws an exception
  • FirstOrDefault returns the first record

Conclusion:

If you want an exception to be thrown if the result set contains many records, use SingleOrDefault.

If you always want 1 record no matter what the result set contains, use FirstOrDefault

 

作者:Chuck Lu    GitHub    
posted @   ChuckLu  阅读(15)  评论(0编辑  收藏  举报
相关博文:
阅读排行:
· 全程不用写代码,我用AI程序员写了一个飞机大战
· DeepSeek 开源周回顾「GitHub 热点速览」
· MongoDB 8.0这个新功能碉堡了,比商业数据库还牛
· 记一次.NET内存居高不下排查解决与启示
· 白话解读 Dapr 1.15:你的「微服务管家」又秀新绝活了
历史上的今天:
2019-08-31 HearthBuddy Ai 调试实战2 在使用海巨人的时候,少召唤了一个图腾(费用是对的)
2019-08-31 HearthBuddy 召唤随从的问题
2019-08-31 五子棋AI教程
2019-08-31 HearthAgent A Hearthstone agent
2019-08-31 Monte Carlo Tree Search – beginners guide
2019-08-31 Programming a Hearthstone agent using Monte Carlo Tree Search(chapter one)
2019-08-31 Add hyperlink to textblock wpf
点击右上角即可分享
微信分享提示