s***o
发帖数: 2191 | 1 While M$ advocates how good its Entiry Framework is, most of the comments I
read from non-M$ people are negative. I didn't pay much attention to this
Framework during the last few months though. Are there any significant
improvments? or at least some promises coming up? Now I get some free time,
is it a good idea to pick up this entiry framework thing, or should I learn
something else instead of wasting time on it?
Any advice? Thanks in advance. |
N********n
发帖数: 8363 | 2 Like everything else, it won't be very useful til 3.0 version. Learn
some WPF / WCF instead.
I
,
learn
【在 s***o 的大作中提到】
: While M$ advocates how good its Entiry Framework is, most of the comments I
: read from non-M$ people are negative. I didn't pay much attention to this
: Framework during the last few months though. Are there any significant
: improvments? or at least some promises coming up? Now I get some free time,
: is it a good idea to pick up this entiry framework thing, or should I learn
: something else instead of wasting time on it?
: Any advice? Thanks in advance.
|
s***o
发帖数: 2191 | 3 So you think Entiry Framework will eventually be uesful and practical?
I am just a little concerned if it has the fate as Linq to Sql had, becoming
a dead monster even before widely accepted.
【在 N********n 的大作中提到】
: Like everything else, it won't be very useful til 3.0 version. Learn
: some WPF / WCF instead.
:
: I
: ,
: learn
|
c**t
发帖数: 2744 | 4 Since our corp is oracle oriented, still waiting for Linq to Oracle, is Linq
to Sql already running to dead end? why?
becoming
【在 s***o 的大作中提到】
: So you think Entiry Framework will eventually be uesful and practical?
: I am just a little concerned if it has the fate as Linq to Sql had, becoming
: a dead monster even before widely accepted.
|
N********n
发帖数: 8363 | 5
Entity Framework is the official ORM of M$. It could be somewhat useful
but I still believe it comes down to how well the underline databases
are designed rather than which ORM you use.
【在 s***o 的大作中提到】
: So you think Entiry Framework will eventually be uesful and practical?
: I am just a little concerned if it has the fate as Linq to Sql had, becoming
: a dead monster even before widely accepted.
|
s***o
发帖数: 2191 | 6 I read several blogs saying this. L2S has gone into "maintenance mode" and
no team inside M$ is working on it. L2S still works in your application but
there will be no further development.
M$ is trying to push developers to use Linq to Entities instead of Linq to
Sql. I know neither in details so I cannot tell how different they are.
Are you sure M$ will release Linq to Oracle if it is not already available?
Linq
【在 c**t 的大作中提到】
: Since our corp is oracle oriented, still waiting for Linq to Oracle, is Linq
: to Sql already running to dead end? why?
:
: becoming
|
d****d
发帖数: 133 | 7 I would still choose Linq to Sql for small projects. If I really need ORM to
handle complicated mappings, I would go for NHibernate instead of EFM. Like
many other people, I don't like the way M$ lays out EFM at all. But
apprantely M$
isn't listening (at least not yet).
As to Linq To Oracle, I saw a projet hosted in Codeplex. Technically anyone
can
write their own custom Linq provider. It doesn't have to depend on M$. We
can
write our Linq To MitBBS if we want.
but
【在 s***o 的大作中提到】
: I read several blogs saying this. L2S has gone into "maintenance mode" and
: no team inside M$ is working on it. L2S still works in your application but
: there will be no further development.
: M$ is trying to push developers to use Linq to Entities instead of Linq to
: Sql. I know neither in details so I cannot tell how different they are.
: Are you sure M$ will release Linq to Oracle if it is not already available?
:
: Linq
|
c**t
发帖数: 2744 | 8 Entities don't support Oracle as well...
but
【在 s***o 的大作中提到】
: I read several blogs saying this. L2S has gone into "maintenance mode" and
: no team inside M$ is working on it. L2S still works in your application but
: there will be no further development.
: M$ is trying to push developers to use Linq to Entities instead of Linq to
: Sql. I know neither in details so I cannot tell how different they are.
: Are you sure M$ will release Linq to Oracle if it is not already available?
:
: Linq
|
c**t
发帖数: 2744 | 9 I knew the codeplex project, it's far away from production use.
to
Like
anyone
【在 d****d 的大作中提到】
: I would still choose Linq to Sql for small projects. If I really need ORM to
: handle complicated mappings, I would go for NHibernate instead of EFM. Like
: many other people, I don't like the way M$ lays out EFM at all. But
: apprantely M$
: isn't listening (at least not yet).
: As to Linq To Oracle, I saw a projet hosted in Codeplex. Technically anyone
: can
: write their own custom Linq provider. It doesn't have to depend on M$. We
: can
: write our Linq To MitBBS if we want.
|
s***o
发帖数: 2191 | 10 So it will not become essential even after the release of the next version,
right?
【在 N********n 的大作中提到】
:
: Entity Framework is the official ORM of M$. It could be somewhat useful
: but I still believe it comes down to how well the underline databases
: are designed rather than which ORM you use.
|
|
|
s***o
发帖数: 2191 | 11 One comment I ever read is something like:
the initial idea of EF as an ORM tool was great. However M$ tried to solve
everyhting with this single Framework, which is impossible and make it a
failure...
to
Like
anyone
【在 d****d 的大作中提到】
: I would still choose Linq to Sql for small projects. If I really need ORM to
: handle complicated mappings, I would go for NHibernate instead of EFM. Like
: many other people, I don't like the way M$ lays out EFM at all. But
: apprantely M$
: isn't listening (at least not yet).
: As to Linq To Oracle, I saw a projet hosted in Codeplex. Technically anyone
: can
: write their own custom Linq provider. It doesn't have to depend on M$. We
: can
: write our Linq To MitBBS if we want.
|
N********n
发帖数: 8363 | 12
If you just need a quick dirty CRUD DB w/o considering of performance,
you can use Entity Framework or any other ORMs. If you do care about
performance, you have to start from designing a sound DB.
【在 s***o 的大作中提到】
: So it will not become essential even after the release of the next version,
: right?
|
s***o
发帖数: 2191 | 13 just tried Entity Framework to build some simple report page, and its
performance is "shocking". With "raw" ADO.NET, the page loads in seconds;
and with Entity Framework approach, it takes more than 1 minutes...
Maybe and hopefully I am using Entity Framework in an "incorrect" way. |
p********l
发帖数: 279 | 14 That's right. Without a good DB design, EF is useless and hard to do mapping.
【在 N********n 的大作中提到】
:
: If you just need a quick dirty CRUD DB w/o considering of performance,
: you can use Entity Framework or any other ORMs. If you do care about
: performance, you have to start from designing a sound DB.
|
c**d
发帖数: 579 | 15 I don't understand why MS came up with so many data access technologies. If
they just focus on L2S or EF, our life will be much easier. |
J*******n
发帖数: 511 | |
c**d
发帖数: 579 | 17 正在琢磨怎么把公司那些几千行的stored procedure转成linq to entities |
c**t
发帖数: 2744 | 18 are you sure this is a good practice? :-)
【在 c**d 的大作中提到】
: 正在琢磨怎么把公司那些几千行的stored procedure转成linq to entities
|
c**d
发帖数: 579 | 19 Which one did you mean, stored procedure or LINQ to Entities?
【在 c**t 的大作中提到】
: are you sure this is a good practice? :-)
|
l*s
发帖数: 783 | 20 如果只是用Linq to Entities来重新包装DAL去call stored procedure问题不大。
如果是说打算用Linq query来重新实现所有的stored procedure就要慎重了。
【在 c**d 的大作中提到】
: Which one did you mean, stored procedure or LINQ to Entities?
|
|
|
c**t
发帖数: 2744 | 21 LINQ to Entities usually has performance issue...
【在 c**d 的大作中提到】
: Which one did you mean, stored procedure or LINQ to Entities?
|
c**d
发帖数: 579 | 22 为啥，从SQL Server 2005起不是dynamic query也cache query plan吗，个人觉得除了
比较
复杂的report没有必要用SP，那些上千行的SP最终是只有写的人知道怎么回事，他要拍
屁股走人其他
人没法维护
【在 l*s 的大作中提到】
: 如果只是用Linq to Entities来重新包装DAL去call stored procedure问题不大。
: 如果是说打算用Linq query来重新实现所有的stored procedure就要慎重了。
|
a9
发帖数: 21638 | 23 sp转了就能读懂了？
【在 c**d 的大作中提到】
: 为啥，从SQL Server 2005起不是dynamic query也cache query plan吗，个人觉得除了
: 比较
: 复杂的report没有必要用SP，那些上千行的SP最终是只有写的人知道怎么回事，他要拍
: 屁股走人其他
: 人没法维护
|
c**d
发帖数: 579 | 24 DBA说SP容易懂，application developer说LINQ query容易懂。我觉得不应该把
business
logic搞到SP里就是
【在 a9 的大作中提到】
: sp转了就能读懂了？
|
a9
发帖数: 21638 | 25 business logic在sp里有它的好处。
linq和sp也没啥太大区别。
【在 c**d 的大作中提到】
: DBA说SP容易懂，application developer说LINQ query容易懂。我觉得不应该把
: business
: logic搞到SP里就是
|
