Integrating both modifications to an object model and...

Details Integrating both modifications to an object model and... Integrating both modifications to an object model and...

2001-01-05

2003-08-19

Alam, Hosain T. (Department: 2172)

Data processing: database and file management or data structures

Database design

Data structure types

C707S793000, C717S106000, C717S120000

Reexamination Certificate

active

06609133

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates generally to data processing systems and, more particularly, to integrating both modifications to an object model and modifications to a database into source code by an object-relational mapping tool.
BACKGROUND OF THE INVENTION
Object-relational mapping tools have been created to facilitate development of application programs that utilize a relational database. A relational database stores data in tables having rows (records) and columns (fields). The tables are usually interrelated, and thus, there is a logical structure imposed on the database. This logical structure is known as a schema. Each table may have a primary key, comprising one or more columns that uniquely identify a row. For example, in a table with rows of customers, a column storing each customer's social security number may be used as the primary key because it uniquely identifies each customer in the table. A table may also have one or more foreign keys, associating a row in one table to one or more rows in another table. For example, where one table contains customer information and another table contains order information for the customers, a foreign key may exist in the order table to relate one customer (or row) in the customer table with one or more orders (or rows) in the order table.
Object-relational mapping tools read database schema information and automatically generate source code from the database. This source code contains a number of classes whose interrelationships reflect the logical structure, or schema, of the database. A class, such as a Java™ class, is a data structure containing both data members that store data and function members (or methods) that act upon the data. The source code may contain one class for each table in the database, and each class may have a data member for each column in the corresponding table. Additionally, the classes contain function members that are used to both get and set the values for the data members and, eventually, update the database.
By using an object-relational mapping tool, a programmer can automatically generate source code to facilitate their database application development. After the source code is generated, the programmer writes code to interact with only the classes in the source code and not the database, thus hiding the complexities of interacting with the database from the programmer. This allows a programmer who is familiar with object-oriented programming to code against familiar classes and not unfamiliar, sometimes cumbersome to use, database query languages.
Although beneficial to programmers, conventional object-relational mapping tools suffer from a limitation. When a programmer runs the object-relational mapping tool, it generates source code with classes that reflect the structure of the database at that time. However, during the lifetime of the database, it is common for a database administrator to change the schema of the database (e.g., add a new field or table). Likewise, it is common for the programmer to update the classes in the source code (e.g., change a field name or delete a field). As such, both the classes and the database tend to evolve and change over time. Conventional object-relational mapping tools, however, are of little help in such situations. These tools can only remap the database to generate classes that contain the database modifications, but which do not contain the programmer's modifications. Therefore, the programmer's changes are lost and must be manually recreated, thus wasting significant development time. It is therefore desirable to improve object-relational mapping tools.


REFERENCES:
patent: 4589092 (1986-05-01), Matick
patent: 5043876 (1991-08-01), Terry
patent: 5261069 (1993-11-01), Wilkinson et al.
patent: 5263155 (1993-11-01), Wang
patent: 5280612 (1994-01-01), Lorie et al.
patent: 5291583 (1994-03-01), Bapat
patent: 5301297 (1994-04-01), Menon et al.
patent: 5504885 (1996-04-01), Alashqur
patent: 5542078 (1996-07-01), Martel et al.
patent: 5548749 (1996-08-01), Kroenke et al.
patent: 5574882 (1996-11-01), Menon et al.
patent: 5583983 (1996-12-01), Schmitter
patent: 5596746 (1997-01-01), Shen et al.
patent: 5732257 (1998-03-01), Atkinson et al.
patent: 5742813 (1998-04-01), Kavanagh et al.
patent: 5765159 (1998-06-01), Srinivasan
patent: 5774731 (1998-06-01), Higuchi et al.
patent: 5829006 (1998-10-01), Parvathaneny et al.
patent: 5835910 (1998-11-01), Kavanagh et al.
patent: 5850544 (1998-12-01), Parvathaneny et al.
patent: 5857197 (1999-01-01), Mullins
patent: 5873093 (1999-02-01), Williamson et al.
patent: 5878411 (1999-03-01), Burroughs et al.
patent: 5878419 (1999-03-01), Carter
patent: 5893108 (1999-04-01), Srinivasan et al.
patent: 5907846 (1999-05-01), Berner et al.
patent: 5920725 (1999-07-01), Ma et al.
patent: 5937409 (1999-08-01), Wetherbee
patent: 5974428 (1999-10-01), Gerard et al.
patent: 5991763 (1999-11-01), Long et al.
patent: 6003040 (1999-12-01), Mital et al.
patent: 6009428 (1999-12-01), Kleewein et al.
patent: 6038565 (2000-03-01), Nock
patent: 6049673 (2000-04-01), McComb et al.
patent: 6175837 (2001-01-01), Sharma et al.
patent: 6182274 (2001-01-01), Lau
patent: 6385618 (2002-05-01), Ng et al.
patent: 0 472 812 (1991-02-01), None
patent: WO 95/03586 (1995-02-01), None
patent: WO 95/04960 (1995-02-01), None
patent: WO 97/03406 (1997-01-01), None
“Fundamentals of Database Systems,” Elmasri et al., Second Edition, 1994, Addison-Wesley Publishing Company, p. 87.*
Fitsilis et al., “Producing Database Schem ata from an Object Oriented Design”, IEEE, pp. 251-257 (1994).
King, Nelson, “Java in the Database Serv er” (Jun. 1998), URL http://www.dbmsmag.com/9806d13.html, pp. 1-8.
Sun Microsystems, “Java Blend Tutorial”, Java Software Division, pp. 1-76 (Jun. 1998).
SQL Tutorial: Introduction to Structured Q uery Language, Version 3.63 (May 1998), URL http://w3.one.net/~jhoffman/sqltut.htm#Compound Conditions.
The JDBC Database Access API (Apr. 1998), URL http://jav a.sun.com/products/jdbc.
O'Brien, Stephen K., “Turbo Pascal 5.5: The Complete Reference”, Osborne/McGraw-Hill (1989), pp. 500-522.
Gosling, Joy, and Steele, “The Java™ Language Specif ication”, Addision-W esley (1996).
Hamilton, Cattell, and Fisher, “JDBC Database Access with Jav a™”, Addison-Wesley (1997).
R.G.G. Cattell et al., “Object Database Standard: O DMG 2.0”, Morgan Kaufmann Publishers, Inc. (1997).
Campione, Mary and Kathy Walrath, “The Java™ Tutorial”, Addison-Wesley (1996).
T. Lindholm and F. Yellin, “The Java Virtual Machine Specification” Second Edition, Apr. 1999, pp. 1-473.
“Customizable Four Pane Lay out for Database Table Definition,” Dec. 1992, pp. 268-269.
H. Bank, “OQL,” Sep. 15, 1997 (Rev. 0.11), pp. 1-7.
“Applications in Java and Extended Java,” Sep. 28, 1998, pp. 1-21.
“Sun Simplifies Database Program ming with Java Blend,” Aug. 21, 1997, pp. 1-3.
S. Wang, “Improvement of Concurrency Control Within Object-Oriented Database Sy stems,” Apr. 5, 1990, IEEE, pp. 68-70.
S. Heiler and S. Zdonik, “Object Views: Extending the Vision,” 1990 IEEE, pp. 86-93.
D. Agrawal, A. Bernstein, P. G upta, and S. Sengupta, “Distributed M ulti-Version Optimistic Concurrency Control for Relational Database,”M ar. 1986, pp. 416-421.
X. Qian and L. Raschid, “Q uery Interoperation Am ong Object-Oriented and Relational Databases,” Mar. 6, 1995, IEEE, pp. 271-278.
S. Gantimahapatruni and G. Karabatis, “Enforcing Data Dependencies in Cooperativ e Information Systems,” May 12, 1993, IEEE, pp. 332-341.
IBM Technical Disclosure Bulletin, vol. 38, No. 01, Jan. 1995, FAST and Secure Stored Procedures for a Client/Server DBMS, pp. 79-82.
A. Alashqur and C. Thompson, “O-R Gateway: A System for Connecting C++ Application Programs and Relational Databases,” Aug. 10, 1992, pp. 151-169.
R. Ahad and T. Cheng, Hewlett-Pack ard Journal 44 (1993) Jun., No. 3, “HP O penODB: An Object-Oriented Database Management System for Commercial Applications,” pp. 20-30.
TOPLink, “The Industry Standard for Persistence Product, A White Paper: The Object People”, 19

Affiliated with

Also associated with

Rating

Integrating both modifications to an object model and... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Integrating both modifications to an object model and..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Integrating both modifications to an object model and... will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3078527