今天做了一次Linq的测试,代码如下:
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
这是个较为复杂的查询,包含两个跨表联合,更重要的是,最终需要的是Count,而并不是整个Blog列表,考验的是Linq的智能程度。
用Sql profile分析,得到对应的SQL是:
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
![None.gif](https://www.cnblogs.com/Images/OutliningIndicators/None.gif)
从上面的SQL可以看出,Linq对代码的分析相当到位,最终着眼于Count,这应该也是得益于Lazy Load。而多表联合查询(对于Channel表和BlogClass表)也做得相当好。从这一个查询应该可以说:Linq的智能度已经相当高了,Linq已经远远超出了傻乎乎拼SQL的水平,值得一试!
鸡蛋里面挑骨头的是,BlogClass 其实和Channel有外键联系的,其实有了BlogClass的限制,Channel就可以不需要了,这是代码中故意加入的一个小Bug,可惜Linq没有自动处理这个Bug的能力,还是进行了两次查询,是不是期望太高了?呵呵。