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

This article mainly introduces "what is the difference between ADO.NET architecture and ADO". In daily operation, I believe many people have doubts about the difference between ADO.NET architecture and ADO. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts about "what is the difference between ADO.NET architecture and ADO?" Next, please follow the editor to study!

ADO.NET architecture

ADO.NET Architecture (object model) has five main objects, namely, Connection, Command, DataAdpter, Dataset and DataReader. The part of these objects in which connections and data operations are established is called 'data Operation object' (Managed Provider), which is composed of Connection object, Command object, DataAdpter object and DataReader object respectively. According to the operation of the image, the most important thing is to make the Dataset image and the beam between the data sources, the data from the data source is extracted and stored in the Dataset object for management, and the data back to the source is stored in the data source.

Connection object: you can open the connection between the program and several sources. Connection was not used to open the image number source, and the data could not be obtained from the data source. Command object: it is used to issue instructions to data sources, such as query, add, modify, delete data, etc.

DataAdpter object: it mainly performs data transfer between data sources and Dataset. It can store the acquired data in dataset for management after issuing orders through command. Dataset object: it can be regarded as a cache, which can retain the data queried in the data source, or even display the whole data according to the data in the source. The ADO.NET architecture can not only store multiple table, but also obtain some table structures such as hosts through DataAdpter objects, and record relationships between tables.

DataReader object: if you only need to sequentially fetch the data in the source and no other operations are required, the ADO.NET architecture can use DataReader object. DataReader object fetching is performed one at a time, and data in the source is fetched down sequentially, and the data captured by the DataReader object is read only, and other operations are not allowed.

The relationship between the components is shown in the following figure:

Differences between ADO.NET Architecture and ADO

For the developers of ADO, the most obvious change is that the Recordset in the previous ADO has disappeared, and it is clearly divided into two types: the traditional DataReader and the traditional DataSet and DataTable, and the development of the subscription tool DataView, which supports the sources of expensive data. this change makes the VB/ASP developers who use ADO have a certain degree of difference, and at the same time makes the academic ADO of the ADO.NET framework somewhat complicated. As a result, some new entrants or VB 6.0/ASP developers will use ADO to access data sources in the .NET Framework when learning the .NET Framework or using VB.NET to develop applications. However, when the .NET Framework application uses the ADO.NET framework,. NET Framework will consume a small part of the application performance because of the additional conversion between COM and .NET data.

At this point, the study on "what is the difference between ADO.NET architecture and ADO" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.