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

This article introduces the relevant knowledge of "what are the batch update steps of ADO.NET". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

In ADO.NET batches, batch updates can only occur on SQL-based data sources. In ADO.NET batches, batch updates can occur on any kind of managed provider, including those that should not expose their data through the SQL query language.

In both cases, data access results in full two-way binding and involves a variety of different objects and methods. You can use command classes such as SqlCommand and OleDbCommand to execute a single command. You can use the data adapter object to download disconnected data and submit updated rowsets. Although the dataset is the container object that the data adapter uses to return and submit record blocks, individual commands return data through the data reader object.

Updates are done through individual commands and stored procedures, and in general, any command text understood by the ADO.NET batch managed provider is generally called an update. The update command always executes new data embedded in the body of the statement. Update commands always require an open connection and may also require an ongoing transaction or a new transaction.

Batch updates are a slightly different branch of methods. At the level of abstraction, you don't issue a command, no matter how complex it may be. Instead, you submit a snapshot of the current row modified on the client and wait for the data source to approve. The key concept behind batch updates is the concept of data disconnection. You download a row table, usually a dataset, modify it on the client as needed, and then submit a new image of these rows to the database server. What you do is commit the changes, not execute a command that creates changes to the data source. This is the essential difference between updates (which I discussed in July column) and batch updates.

The following figure illustrates the double update architecture of an ADO.NET application.

Before discussing ADO.NET batch updates in further detail, I need to clarify an aspect of the batch update model that often leads to some misunderstanding. Although updates and batch updates differ substantially in their actual implementation within ADO.NET, they follow the same update model. Both updates and batch updates are done through direct and provider-specific statements.

Of course, because batch updates usually involve more rows, these statements are combined into one batch call. Batch updates cycle through the rows of the target dataset from beginning to end, issuing the appropriate update command (INSERT, DELETE, or UPDATE) whenever updated rows are found. When communicating with updated rows, the ADO.NET batch runs a predefined direct SQL command. In essence, this is batch update.

This is the end of the content of "what are the batch update steps for ADO.NET". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.