Browse Prior Art Database

Controlled Rollback for Structured Query Language

IP.com Disclosure Number: IPCOM000110071D
Original Publication Date: 1992-Oct-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 3 page(s) / 76K

Publishing Venue

IBM

Related People

Jacobs, DC: AUTHOR [+3]

Abstract

A method is described which will provide the ability to, in the Structured Query Language (SQL) database environment, "rollback" a specified number of SQL statements in a unit of work (UOW).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Controlled Rollback for Structured Query Language

       A method is described which will provide the ability to,
in the Structured Query Language (SQL) database environment,
"rollback" a specified number of SQL statements in a unit of work
(UOW).

      In the SQL environment, units of work are comprised of a number
SQL statements.  These units of work are bounded by a COMMIT or
ROLLBACK SQL statement which completes each UOW and starts the next.
If a COMMIT statement is issued and completes successfully, the
entire unit of work is marked in the database log file as permanent
changes to the database.  If a ROLLBACK statement is issued and
completes successfully, the entire UOW is backed out and no changes
to the database occur.

      As stated, when the ROLLBACK statement is issued the entire
transaction is backed out.  The current syntax for the ROLLBACK
statement is as follows:

                            (Image Omitted)

To illustrate the problem consider the following example:
         Begin UOW
            Exec SQL statement 1
            Exec SQL statement 2
            Exec SQL statement 3
            Exec SQL statement 4
            Exec SQL statement 5
         Rollback UOW

      An application could be set up in such a way that each screen
provides for interactive input from a user.  The information  from
these  screens would  provide  data  which would be used for each
distinct SQL statement.  Using the above example, screen 1 would
provide information for SQL statement 1 and so forth.  If the user
recognizes that an error was made in SQL statement 3 and was
currently inputting information from the S...