Detecting an integrity constraint violation in a database by analyzing database schema, application and mapping and inserting a check into the database and application

• US 7,519,952 B2
• Filed: 07/28/2003
• Issued: 04/14/2009
• Est. Priority Date: 07/28/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Shmueli, Oded, Raghavachari, Mukund, Bordawekar, Rajesh, Burke, Michael George
• Primary Examiner(s): YAARY, MICHAEL D
• Application Number:
  US10/627,982
• Publication Number:
  US 20050027542A1
• Time in Patent Office: 2,087 Days
• Field of Search: 717/100, 717124-127, 717/133, 717/313, 717/4, 717/5, 707/100, 707/102, 707/101, 707/2, 707/3, 707/4, 707/5, 707/103.R, 707/104.1, 707/103.Y, 715/513, 715/514, 719/313
• US Class Current: 717/124
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A system (and method) of detecting an error in a database interaction, includes providing information about at least one of at least first and second software systems, and a mapping between at least a portion of said at least first and second software systems; and examining said at least one of said first and second software systems and said mapping to determine an error in an interaction between said at least first and second software systems.

Claims

1. A system while executing on a computer for detecting an integrity constraint violation in a database interaction, comprising:

a common constraint model for analyzing database schema, application type, and a mapping between said database schema and said application type;

a generating unit for generating a check based upon said database schema, said application type, and said mapping;

an inserting unit for inserting said check into one of said database and said application; and

a determining unit for determining whether an integrity constraint violation will occur in said database interaction with said application based upon said check.

2. A method of constructing a program, comprising:

detecting, in an application, portions of said application code that will or may raise a database integrity constraint violation during an application-database interaction during runtime, the detecting including examining database schema, examining application type, and a mapping between the database schema and the application type;

generating an integrity check based upon said database schema, said application type, and said mapping;

inserting said integrity check notifying a programmer of such a definite or potential violation; and

completing the program.