Browse Prior Art Database

No Logging on a Read-Only Transaction

IP.com Disclosure Number: IPCOM000103464D
Original Publication Date: 1990-Dec-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 1 page(s) / 31K

Publishing Venue

IBM

Related People

Atkinson, RL: AUTHOR [+5]

Abstract

Disclosed is a method to prevent the logging of any data to the Database Log for a database transaction that only accesses the database in a read-only fashion.

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

No Logging on a Read-Only Transaction

      Disclosed is a method to prevent the logging of any data to the
Database Log for a database transaction that only accesses the
database in a read-only fashion.

      A transaction table is maintained by the Database Manager to
track the state of all active transactions using a database.  The
current state of the transaction may be READ, WRITE, COMMIT or ABORT.
When a new transaction is started, the state is initially set to
READ.  When the transaction first causes a log record to be written
to the Database Log, the state is set to WRITE.

      If the state of a transaction is READ when it commits or
aborts, the normal commit or abort log records are not written to the
Database Log. All other commit or abort processing is performed such
as releasing any database locks held by the transaction.

      This invention allows for use of a read-only database on a
diskette with a write-protect tab.  It also allows several
applications to access a database in a read-only fashion without the
need to write any log records to the Database Log.

      Disclosed anonymously.