All geek questions in one place

What's better? Working with a dataset or database

I develop many applications and am confused about using a dataset. Until the date, I do not use a dataset or run my application directly from my database using the queries and procedures that are executed in the Database Engine.

But I would like to know what good practice is using a dataset? or work address in the database.

Plz try to give me certain cases and when to use the data set along with the operation (Insert / Update)

you can set the read / write lock in the data set in our database

+3
source share
5 answers

, . , db, CRUD-. , . , -. , , . , .

+5

, MVC , DataSet, .

, . , , . ? <Pshaw> .

, ORM , . , , DataSet, . .

+2

, , , .. - .. . , , (, A, B C, A, B C ), , , , ( OMGPonies). , , , "" , , . , ... ROT!

.Net / (, ) ( , ), "" , .net- .. ( , , , ).

+1

, , 7 ( , ).

, , , . ORM, NHibernate Entity Framework, CRUD. , - .

, , , , , , .

0

, DataSets .

Actually, if your objects are O / R-mapped and use serialization and generics, you never need DataSets.

But a DataSet is great for reporting.

This is due to the fact that the reports do not have a specific structure that can or should be displayed O / R.

I use DataSets only in tandem with reporting tools.

0
source

Source: https://habr.com/ru/post/1726141/

More articles:


All Articles