Method and system for detection of integrity constraint violations
First Claim
Patent Images
1. A method for detecting an error in an interaction between a plurality of software systems, the method comprising:
- 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;
automatically generating a check based upon the information and the mapping;
inserting said check into at least one of said first and second software systems;
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 based upon said check; and
providing a shadow database in one of said at least first and second software systems,wherein said shadow database contains partial knowledge of the other of said at least first and second software systems and being used to perform a check, andwherein said partial knowledge includes at least one of;
partial knowledge of data values in said other of said at least first and second software systems; and
partial knowledge of a non-existence of data values in said other of said at least first and second software systems.
0 Assignments
0 Petitions
Accused Products
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 the at least first and second software systems, and examining the at least one of the first and second software systems and the mapping to determine an error in an interaction between the at least first and second software systems.
-
Citations
23 Claims
-
1. A method for detecting an error in an interaction between a plurality of software systems, the method comprising:
-
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; automatically generating a check based upon the information and the mapping; inserting said check into at least one of said first and second software systems; 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 based upon said check; and providing a shadow database in one of said at least first and second software systems, wherein said shadow database contains partial knowledge of the other of said at least first and second software systems and being used to perform a check, and wherein said partial knowledge includes at least one of; partial knowledge of data values in said other of said at least first and second software systems; and partial knowledge of a non-existence of data values in said other of said at least first and second software systems. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A method of detecting an error in a database interaction, the method comprising:
-
examining database code for database constraints; examining an application code for application-level constraints; automatically generating a check based upon said database constraints and said application-level constraints; inserting said check into at least one of said database code and said application code; analyzing a mapping between said database code and said application code, to determine an error in a database interaction, based upon said check; after determining said integrity constraint violation and prior to running a program including said application, raising a notification; at runtime of said program, when an integrity constraint violation is determined to occur, raising a notification; and analyzing a common constraint model receiving said database schema, application type, and mapping, to determine an inconsistency between said database schema and said application type, wherein if no said inconsistency is determined, then taking all of common constraints and analyzing the application code with respect to the common constraints for an error in the application code, wherein if no said error is determined in the application code, then inserting a check into said application code to enforce the constraints at runtime. - View Dependent Claims (13, 14, 15, 16, 17, 18)
-
-
19. A method of detecting an integrity constraint violation in a database interaction, the method comprising:
-
examining a database schema; examining an application type; automatically generating a check based upon said database schema and said application type; inserting said check into one of said database schema and said application type; analyzing a mapping between said database schema and said application type, to determine whether an integrity constraint violation will occur in said database interaction with said application based upon said check; after determining said integrity constraint violation and prior to running a program including said application, raising a notification; at runtime of said program, when an integrity constraint violation is determined to occur, raising a notification; and analyzing a common constraint model receiving said database schema, application type, and mapping, to determine an inconsistency between said database schema and said application type, wherein if no said inconsistency is determined, then taking all of common constraints and analyzing the application code with respect to the common constraints for an error in the application code, wherein if no said error is determined in the application code, then inserting a check into said application code to enforce the constraints at runtime, wherein said application type includes application code including integrity constraints defined therein, and wherein said database schema provides each of the integrated constraints defined in the database. - View Dependent Claims (20, 21)
-
-
22. A system of detecting an error in a database interaction, comprising:
-
a module for examining, as performed by a processor on a computer, a database code for database constraints; a module for examining an application code for application-level constraints; a module for automatically generating a check based upon said database constraints and said application-level constraints; a module for inserting said check into one of said database code and said application code; an analyzing unit for analyzing a mapping between said database code and said application code, to determine an error in a database interaction based upon said check; a module for, after determining said integrity constraint violation and prior to running a program including said application, raising a notification; a module for, at runtime of said program, when an integrity constraint violation is determined to occur, raising a notification; and a module for analyzing a common constraint model receiving said database schema, application type, and mapping, to determine an inconsistency between said database schema and said application type, wherein if no said inconsistency is determined, then taking all of common constraints and analyzing the application code with respect to the common constraints for an error in the application code, wherein if no said error is determined in the application code, then inserting a check into said application code to enforce the constraints at runtime.
-
-
23. A method for detecting an error in an interaction between a plurality of software systems, the method comprising:
-
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; automatically generating a check based upon the information and the mapping; inserting said check into at least one of said first and second software systems; statically 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; and providing a shadow database in one of said at least first and second software systems, wherein said shadow database contains partial knowledge of the other of said at least first and second software systems and being used to perform a check, and wherein said partial knowledge includes at least one of; partial knowledge of data values in said other of said at least first and second software systems; and partial knowledge of a non-existence of data values in said other of said at least first and second software systems.
-
Specification