Home > Articles > Programming > Windows Programming

  • Print
  • + Share This
This chapter is from the book

Programmatic Transactions

In this chapter, the database that was created earlier is reused. Just as a reminder, the database diagram is shown again in Figure 7-2.

Figure 7.2

Figure 7-2 Sample database.

With serviced components, you can do transactions by using attributes. Before looking into these attributes, however, let’s take a look at how transactions are done programmatically so that you can easily compare the techniques.

Using the .NET data provider for SQL Server, you can do transactions programmatically with the SqlTransaction class. A new transaction is created with the method BeginTransaction of the SqlConnection class, which returns an object of type SqlTransaction. Then the SqlTransaction methods Commit and Rollback can be used to commit or to undo the transaction result.

Let’s immediately consider an example, with the class CourseData. A connection string is passed into the constructor of this class, as shown in Listing 7-1. The caller of this class can read the connection string from a configuration file if required. To avoid creating a new SqlCommand with every method call, a new SqlCommand is instantiated in the constructor, and the parameters that are needed to add a new course record are added to the command object.

Listing 7-1 Programmatic Transactions

using System;
using System.Data;
using System.Data.SqlClient;
namespace Samples.Courses.Data
{
   public class CourseData
   {
      private string connectionString;
      private SqlCommand insertCourseCommand;
      public CourseData(string connectionString)
      {
         this.connectionString = connectionString; 
         insertCourseCommand = new SqlCommand();
         insertCourseCommand.CommandText = "INSERT INTO " + 
               "Courses (CourseId, Number, Title, Active) " + 
               "VALUES(@CourseId, @Number, @Title, @Active)";
         insertCourseCommand.Parameters.Add("@CourseId", 
               SqlDbType.UniqueIdentifier);
         insertCourseCommand.Parameters.Add("@Number", 
               SqlDbType.NChar, 10);
         insertCourseCommand.Parameters.Add("@Title", 
               SqlDbType.NVarChar, 50);
         insertCourseCommand.Parameters.Add("@Active",
               SqlDbType.Bit);
      }

In the method AddCourse that is shown in Listing 7-2, the connection object is instantiated, the connection is associated with the previously created command object, and the connection is opened. Inside a try block, the INSERT statement is executed with the method ExecuteNonQuery. Before that, a new transaction is started using the connection.BeginTransaction method. The returned transaction object is automatically associated with the connection. If the database insert is successfully, the transaction is committed. If an exception is thrown within ExecuteNonQuery because of some error while issuing the database insert, the exception is caught, and a rollback is done in the catch block.

Listing 7-2 AddCourse Method with Programmatic Transactions

public void AddCourse(Course course)
      {
         int customerId = -1;
         SqlConnection connection = 
               new SqlConnection(connectionString);
         insertCourseCommand.Connection = connection;
         insertCourseCommand.Parameters["@CourseId"].Value = 
               course.CourseId;
         insertCourseCommand.Parameters["@Number"].Value = 
               course.Number;
         insertCourseCommand.Parameters["@Title"].Value = 
               course.Title;
         insertCourseCommand.Parameters["@Active"].Value =
               course.Active;
         connection.Open();
         try
         {
            insertCourseCommand.Transaction = 
                  connection.BeginTransaction();
            insertCourseCommand.ExecuteNonQuery();
            insertCourseCommand.Transaction.Commit();
         }
         catch
         {
            insertCourseCommand.Transaction.Rollback();
            throw;
         }
         finally
         {
            connection.Close();
         }
      }

In the Test class of the client application (Figure 7-3), the class CourseData is used to create a new course. The connection string passed to the constructor is read from the configuration file using the ConfigurationSettings class.

Listing 7-3 Client Test Application

using System;
using System.Configuration;
using Samples.Courses.Data;
using Samples.Courses.Entities;
class Test
{
   static void Main()
   {
      // read the connection string from the configuration file
      string connectionString = 
            ConfigurationSettings.AppSettings["Database"];
      // write a new course to the database
      CourseData db = new CourseData(connectionString);
      Course c = new Course();
      c.Number = "MS-2389";
      c.Title = "Programming ADO.NET";
      c.Active = true;
      db.AddCourse(c);
   }
}

Listing 7-4 shows the application configuration file that is used by the client application. In the configuration, the database connection string is defined as a child element of <appSettings>.

Listing 7-4 Application Configuration File to Define the Connection String

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="Database" 
        value="server=localhost;database=Courses;
        trusted_connection=true" />
  </appSettings>
</configuration>

As shown in the previous examples, dealing with transactions programmatically is not a hard task. However, how can the implementation be done if multiple SQL commands should be part of a single transaction? If all these commands are closely related, putting them into a single try block is not a big deal. However, a scenario in which a single transaction should cross multiple components is not so straightforward.

If multiple classes should participate in the same transaction (for example, a customer should be added, and an entry to the course map must also be done), dealing with transactions is not that easy anymore. Take a look at how this can be handled.

Figure 7-3 shows a scenario where a single transaction is useful: If one course attendee wants to change her course schedule, she must be removed from one course list and added to another one. Now it should never happen that the course attendee is added to the new course, but not deleted from the previous one, and it should never happen that the attendee is just removed from a course, but never added to the new course. Both adding and removing the attendee from the course must be part of the same transaction.

Figure 7.3

Figure 7-3 Transactions with multiple components.

You can program multiple database actions that are spread across multiple classes, and that should participate in the same transaction, by passing the connection object that is associated with the transaction as an argument to the methods. Inside the methods, the same connection object can be used to participate within the same transaction.

This can get quite complex with many classes and bigger scenarios. You have to decide whether the class should participate in the same transaction, or whether a new transaction should be started. What should happen if an object is called in between that does not use database methods at all? With such a method, it would be necessary to add an additional argument so that the connection object could be passed.

Enterprise Services offers a way to deal with this complexity: automatic transactions.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020