w*s
发帖数: 7227 | | x**n
发帖数: 461 | 2 dataset: a collection of data that know how to persist themselves, refer to
active record.
Entity data model: model the domain.
LINQ: query the data.
Entity Framework: an OR/M library with extra features. | w*s
发帖数: 7227 | 3 大牛，什么情况用dataset,什么情况用别的？
现在趋势是什么？
to
【在 x**n 的大作中提到】
: dataset: a collection of data that know how to persist themselves, refer to
: active record.
: Entity data model: model the domain.
: LINQ: query the data.
: Entity Framework: an OR/M library with extra features.
| s***o
发帖数: 2191 | 4 Dataset is a component from ADO.NET. You can think it as a mini in-memory
database (that maps to part of your back end database). It is very "
heavyweight" so you'd better consider other approaches first. It's still
useful in some situations, for example, when you do "bulk" operations.
Linq is a very important language feature that you will use everyday. But if
you mean "Linq to Sql", then ignore it. You have Entity Framework now.
For "entity data model", I assume you mean EDM in entity framework. Usually
you don't have to dig into such low level concepts to be able to use EF,
especially when you take the "Code First" approach, which is also my
suggestion.
Use EF (or nHibernate) as the primary data access technique, go back to the
raw ADO.NET when performance is critical or the problem domain is very
complex (possibly with the help of micro ORMs such as Dapper, Massive, etc).
That's the way I would go.
【在 w*s 的大作中提到】
: 晕头转向了，他们是什么关系，趋势如何？
| x**n
发帖数: 461 | 5 There is no 大牛 in this world. The difference is just experiences.
If your platform has native support for active record, you may use dataset.
Generally, if your system is simple enough, you may go dataset. Most time,
if starting from domain modeling, and you want your domain model(the core of
your application) to exist for long time, model it as persistence ignorance
(PI), not knowing how to persist itself. Then use OR/M to map it to
persistence (most time it is relational database). The most popular choices
are EF and NHibernate.
By the way, why not ask on the .net board? There are more people talking
about .net tech than here.
【在 w*s 的大作中提到】
: 大牛，什么情况用dataset,什么情况用别的？
: 现在趋势是什么？
:
: to
| w*s
发帖数: 7227 | 6 thanks a lot !
btw, didn't know there's a .net board.
of
ignorance
choices
【在 x**n 的大作中提到】
: There is no 大牛 in this world. The difference is just experiences.
: If your platform has native support for active record, you may use dataset.
: Generally, if your system is simple enough, you may go dataset. Most time,
: if starting from domain modeling, and you want your domain model(the core of
: your application) to exist for long time, model it as persistence ignorance
: (PI), not knowing how to persist itself. Then use OR/M to map it to
: persistence (most time it is relational database). The most popular choices
: are EF and NHibernate.
: By the way, why not ask on the .net board? There are more people talking
: about .net tech than here.
|
|
