Shulou(Shulou.com)06/02 Report--

This article mainly explains "which objects can be described by ADO.NET". Friends who are interested may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn what objects can be described by ADO.NET.

ADO.NET description object

Command object can mainly be used to issue some instructions to the database, such as query, add, modify, delete data and other instructions, as well as call stored programs in the database and so on. This object is structured on the Connection object, that is, the Command object is linked to the data source

DataSetCommand object

The DataSetCommand object mainly performs the work of data transfer between the data source and the DataSet. It can issue commands through the Command object and put the obtained data into the DataSet object. This object is structured on top of a Command object and provides a lot of functionality for use with DataSet. In Beta version 2, the DataSetCommand object is renamed to DataAdapter.

DataSet object

The object DataSet can be regarded as a temporary storage area (Cache), which can retain the data queried from the database and even display the entire database. The ability of DataSet is not only to store multiple Table, but also to obtain some data table structures such as primary keys through DataSetCommand objects, and to record the relationships between data tables.

DataSet objects can be said to be heavyweight objects in ADO.NET. ADO.NET describes that this object is structured on DataSetCommand objects and does not have the ability to communicate with data sources; that is to say, we use DataSetCommand objects as a bridge to transfer data between DataSet objects and data sources.

DataReader object

The DataReader object can be used when we only need to read the data sequentially and no other operations are needed. The DataReader object only reads the data in the data source one stroke at a time, and the data is read-only and no other operations are allowed.

Because DataReader is limited to one stroke at a time when reading data, and can only be read-only, it is not only resource-saving but also efficient to use. In addition to being more efficient in using DataReader objects, you can reduce the load on the network because you don't have to send all the data back.

At this point, I believe you have a deeper understanding of "which objects can be described by ADO.NET". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.