为了完全掌握EF（实体框架）的所有概念，我需要有多深入的T-SQL知识？
更确切地说，目前我对SQL的了解并不小。 我非常了解所有基础知识以及一些中间概念，如存储过程，UDF，trigers等。
但是，我是否需要了解诸如XQuery和XPath，SQL CLR编程或目录视图和动态管理视图之类的内容才能完全理解EF，或者这不需要这样，因为EF有自己实现同样的方法吗？
我希望你没有发现这个愚蠢的问题因为我对EF的新手知识会节省一些时间。
我必须补充一点，我不是数据库管理员，也不是（至少现在），而是.NET开发人员学习EF。
How deep knowledge of T-SQL do I need to have in order to fully grasp all concepts of EF (Entity Framework)?
To be more precise, currently my knowledge of SQL is not small. I know all the basics very well as well as some intermediate concepts like stored procedures, UDF, trigers etc.
But do I need to know things such as XQuery and XPath, SQL CLR Programming or Catalog Views and Dynamic Management Views to fully understand EF or this is not needed as EF has it's own way of achieving the same thing?
I hope you don't find this question stupid as it will save me some time due to my novice knowledge of EF.
I have to add that I am not a database administrator nor will I be (at least for now) but a .NET developer learning EF.
最满意答案
基本上，你必须更少了解EF而不是没有它。 它部分地保护您免受底层数据库技术的影响。 你不得不接受权衡取舍你知道的越少（性能更差或设计不合理）。 但是你不需要你引用的任何东西：
但是，我是否需要了解诸如XQuery和XPath，SQL CLR编程或目录视图和动态管理视图之类的内容才能完全理解EF，或者这不需要这样，因为EF有自己实现同样的方法吗？
因为大多数情况下，EF不支持它们......
Basically, you have to know less with EF than without it. It shields you partially from the underlying database technology. You kind of have to accept trade-offs the less you know (worse performance or inelegant design). But you don't need any of the things you quoted:
But do I need to know things such as XQuery and XPath, SQL CLR Programming or Catalog Views and Dynamic Management Views to fully understand EF or this is not needed as EF has it's own way of achieving the same thing?
Because mostly, they are not supported by EF anyway...
我需要多深入了解TSQL才能完全掌握实体框架中的所有内容？(How deep do I need to know TSQL to fully grasp everything in Entity Framework? [closed])为了完全掌握EF（实体框架）的所有概念，我需要有多深入的T-SQL知识？
更确切地说，目前我对SQL的了解并不小。 我非常了解所有基础知识以及一些中间概念，如存储过程，UDF，trigers等。
但是，我是否需要了解诸如XQuery和XPath，SQL CLR编程或目录视图和动态管理视图之类的内容才能完全理解EF，或者这不需要这样，因为EF有自己实现同样的方法吗？
我希望你没有发现这个愚蠢的问题因为我对EF的新手知识会节省一些时间。
我必须补充一点，我不是数据库管理员，也不是（至少现在），而是.NET开发人员学习EF。
How deep knowledge of T-SQL do I need to have in order to fully grasp all concepts of EF (Entity Framework)?
To be more precise, currently my knowledge of SQL is not small. I know all the basics very well as well as some intermediate concepts like stored procedures, UDF, trigers etc.
But do I need to know things such as XQuery and XPath, SQL CLR Programming or Catalog Views and Dynamic Management Views to fully understand EF or this is not needed as EF has it's own way of achieving the same thing?
I hope you don't find this question stupid as it will save me some time due to my novice knowledge of EF.
I have to add that I am not a database administrator nor will I be (at least for now) but a .NET developer learning EF.
最满意答案
基本上，你必须更少了解EF而不是没有它。 它部分地保护您免受底层数据库技术的影响。 你不得不接受权衡取舍你知道的越少（性能更差或设计不合理）。 但是你不需要你引用的任何东西：
但是，我是否需要了解诸如XQuery和XPath，SQL CLR编程或目录视图和动态管理视图之类的内容才能完全理解EF，或者这不需要这样，因为EF有自己实现同样的方法吗？
因为大多数情况下，EF不支持它们......
Basically, you have to know less with EF than without it. It shields you partially from the underlying database technology. You kind of have to accept trade-offs the less you know (worse performance or inelegant design). But you don't need any of the things you quoted:
But do I need to know things such as XQuery and XPath, SQL CLR Programming or Catalog Views and Dynamic Management Views to fully understand EF or this is not needed as EF has it's own way of achieving the same thing?
Because mostly, they are not supported by EF anyway...
发布评论