|
References  |
|
|
| *references marked with an asterisk below are user-added references |
|
U.S. References |
|
|
| Add a new US reference: |
| | Reference | Relevancy | Comments | Reference | Relevancy | Comments | 5835909 Alter
Nov,1998 |      Your vote accepted [0 after 0 votes] | | 5794030 Morsi et al.
Aug,1998 |      Your vote accepted [0 after 0 votes] | | 5715441 Atkinson et al.
Feb,1998 |      Your vote accepted [0 after 0 votes] | | 5706504 Atkinson et al.
Jan,1998 |      Your vote accepted [0 after 0 votes] | | 5680618 Freund
Oct,1997 |      Your vote accepted [0 after 0 votes] | | 5657259 Davis et al.
Aug,1997 |      Your vote accepted [0 after 0 votes] | | 5649101 Mathewson, II
Jul,1997 |      Your vote accepted [0 after 0 votes] | | 5652876 Ashe et al.
Jul,1997 |      Your vote accepted [0 after 0 votes] | | 5627996 Bauer
May,1997 |      Your vote accepted [0 after 0 votes] | | 5625816 Burdick et al.
Apr,1997 |      Your vote accepted [0 after 0 votes] | | 5625465 Lech et al.
Apr,1997 |      Your vote accepted [0 after 0 votes] | | 5600836 Alter
Feb,1997 |      Your vote accepted [0 after 0 votes] | | 5603027 Ohkami
Feb,1997 |      Your vote accepted [0 after 0 votes] | | 5600833 Seen et al.
Feb,1997 |      Your vote accepted [0 after 0 votes] | | 5559954 Sakoda et al.
Sep,1996 |      Your vote accepted [0 after 0 votes] | | 5548753 Linstead et al.
Aug,1996 |      Your vote accepted [0 after 0 votes] | | 5539918 Allen et al.
Jul,1996 |      Your vote accepted [0 after 0 votes] | | 5535386 Wang
Jul,1996 |      Your vote accepted [0 after 0 votes] | | 5526518 Kashio
Jun,1996 |      Your vote accepted [0 after 0 votes] | | 5517670 Allen et al.
May,1996 |      Your vote accepted [0 after 0 votes] | | 5504879 Eisenberg et al.
Apr,1996 |      Your vote accepted [0 after 0 votes] | | 5511188 Pascucci et al.
Apr,1996 |      Your vote accepted [0 after 0 votes] | | 5495561 Holt
Feb,1996 |      Your vote accepted [0 after 0 votes] | | 5446880 Balgeman et al.
Aug,1995 |      Your vote accepted [0 after 0 votes] | | 5347653 Flynn et al.
Sep,1994 |      Your vote accepted [0 after 0 votes] | | 5280612 Lorie et al.
Jan,1994 |      Your vote accepted [0 after 0 votes] | | 5058000 Cox et al.
Oct,1991 |      Your vote accepted [0 after 0 votes] | | 4686522 Hernandez et al.
Aug,1987 |      Your vote accepted [0 after 0 votes] | | 4558413 Schmidt et al.
Dec,1985 |      Your vote accepted [0 after 0 votes] | | | | | |
|
|
|
|
U.S. References |
|
|
Foreign References |
|
|
|
|
|
|
Foreign References |
|
|
Other References |
|
|
| Add a new Other reference: |
| Post related web sites and other references in this section |
| | Reference | Relevancy | Comments | Elisa Bertino, Lorenzo Martino, Object-Oriented Database Management Systems: Concepts and Issues, Apr. 1991, pp. 33-47.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Charles W. Krueger, Software Reuse, ACM Computing Surveys, vol. 24, No. 2, Jun. 1992, pp. 132-183.
. May,2007 |      Your vote accepted [0 after 0 votes] | | K. Narayanaswamy, K.V. Bapa Rao, An Incremental Mechanism for Schema Evolution in Engineering Domains, 1988, pp. 294-301.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Simon Monk, Ian Sommerville, Schema Evolution in OODBs Using Class Versioning, Sigmod Record, vol. 22, No. 3, Sep. 1993, pp. 16-22.
. May,2007 |      Your vote accepted [0 after 0 votes] | | J.F. Roddick, Dynamically Chaning Schemas Within Database Models, The Austrailian Computer Journal, vol. 23, No. 3, Aug. 1991, pp. 105-109.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Jay Banerjee, Won Kim, Hyoung-Joo Kim, Henry F. Korth, Semantics and Implementation of Schema Evolution in Object-Oriented Databases, 1987, pp. 311-322.
. May,2007 |      Your vote accepted [0 after 0 votes] | | David Beech, Brom Mahbod, Generalized Version Control in an Object-Oriented Database, 1988, pp. 14-22.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Simon Gibbs, Dennis Tsichritzis, Eduardo Casais, Oscar Nierstrasz, Xavier Pintado, Class Management for Software Communities, Communications of the ACM, vol. 33, No. 9, Sep. 1990, pp. 91-103.
. May,2007 |      Your vote accepted [0 after 0 votes] | | G.T. Nguyen, D. Rieu, Schema Evolution in Object-Oriented Database Systems, Data & Knowledge Engineering, 4 (1989), pp. 43-67.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Barbara Staudt Lerner, A. Nico Habermann, Beyong Schema Evolution to Database Reorganization, Oopsla Ecoop '90 Proceedings, Conference on Object-Oriented Programming: Systems, Languages, and Applications, European Conference on Object-Oriented
Programming, Sigplan Notices, vol. 25, No. 10, Oct. 1990, pp. 67-76.
. May,2007 |      Your vote accepted [0 after 0 votes] | | D. Jason Penney, Jacob Stein, Class Modification inthe GemStone Object-Oriented DBMS, Oopsla '87 Proceedings, Oct. 4-8, 1987, pp. 111-117.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Lichao Tan, Takuya Katayama, Meta Operations for Type Management in Object-Oriented Databases--A Lazy Mechanism for Schema Evolution, Deductive and Object-Oriented Databases, 1990, pp. 241-258.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Stanley B. Zdonik, Object-Oriented Type Evolution, Advances in Database Programming Languages, pp. 277-288.
. May,2007 |      Your vote accepted [0 after 0 votes] | | John F. Roddick, Schema Evolution in Database Systems--An Annotated Bibliography, Sigmod Record, vol. 21, No. 4, Dec. 1992, pp. 35-39.
. May,2007 |      Your vote accepted [0 after 0 votes] | | Andrea J. Skarra, Stanley B. Zdonik, The Management of Chaning Types in an Object-Oriented Database, Ooplsla '86 Proceedings, Sep. 1986, pp. 483-495.. May,2007 |      Your vote accepted [0 after 0 votes] | | |
|
|
|
|
Other References |
|
|
|
|
|
References  |
|
|
Claims  |
|
|
What is claimed is:
1. A method for supplying data to an application, the method comprising the computer-implemented steps of:
receiving a request initiated by the application for stored data to be supplied to the application;
in response to the request to supply the stored data to the application,
performing the steps of
determining a first format, said first format being the format in which said stored data is stored, and
determining a second format, said second format being the format in which said application expects to receive said stored data;
creating a target instance of said stored data by converting said stored data from said first format to said second format without said application that requested the stored data or users of the application that requested the stored data knowing
the format in which the stored data is stored; and
supplying said target instance to the application that requested the stored data.
2. The method of claim 1 wherein the step of determining the second format comprises the steps of:
determining a data type that corresponds to said stored data;
determining a first version identifier that identifies a version of said data type that said application uses;
searching for a first schema version record that corresponds to said data type;
comparing a second version identifier in said first schema version record with said first version identifier;
if said second version identifier matches said first version identifier, then reading data that describes said second format from format data contained in said first schema version record;
if said second version identifier does not match said first version identifier, then
finding a second schema version record that is associated with said data type and which contains said first version identifier; and
reading data that describes said second format from format data contained in said second schema version record.
3. The method of claim 2 wherein the step of searching for a first schema version record comprises the steps of:
determining a type identifier that uniquely identifies said data type; and performing a search on a plurality of schema version records based on said type identifier.
4. The method of claim 1 wherein the step of determining the second format comprises the steps of:
determining a data type that corresponds to said stored data;
determining a first version identifier that identifies a version of said data type that said application uses;
using said data type and first version identifier to locate an entry in a table; and
using information in said entry to locate a schema version record that specifies said second format.
5. The method of claim 2 where in the step of determining the first version identifier includes the steps of:
inspecting an entry associated with said data type in a type version table associated with said application; and
reading said first version identifier from said entry.
6. The method of claim 5 further comprising the step of causing said application to build said type version table upon initialization by:
causing an initialization routine with in the application to call registration routines for a plurality of libraries used by said application; and
causing said registration routines to add entries to said type version table to indicate which versions of data types are used by said plurality of libraries.
7. The method of claim 1 wherein said step of determining said first format includes the steps of:
determining a data type that corresponds to said stored data;
determining a first version identifier that identifies a version of said data type that was used to store said stored data;
searching for a first schema version record that corresponds to said data type;
comparing a second version identifier in said first schema version record with said first version identifier;
if said second version identifier matches said first version identifier, then reading data that describes said first format from format data contained in said first schema version record;
if said second version identifier does not match said first version identifier, then
finding a second schema version record that is associated with said data type and which contains said first version identifier; and
reading data that describes said first format from format data contained in said first schema version record.
8. The method of claim 7 wherein said step of determining said first version identifier includes the step of reading schema version information stored with said stored data.
9. The method of claim 1 wherein the step of converting said stored data from said first format to said second format includes the step of:
comparing attributes specified in said first format with attributes specified in said second format;
if an attribute exists in said first format and said second format, then copying data for said attribute from said stored data to said target instance;
if an attribute exists in said second format but not said first format, then storing a default value for said attribute in said target instance;
if an attribute exists in said first format but not in said second format, then not copying data that corresponds to said attribute from said stored data to said target instance.
10. The method of claim 9 wherein the step of copying data for said attribute comprises the steps of:
determining whether said attribute has an identical format in said first format and said second format;
if said attribute has an identical format in said first format and said second format, then copying data for said attribute from said stored data to said target instance without performing any conversion operation; and
if said attribute does not have an identical format in said first format and said second format, then
reading data for said attribute from said stored data;
performing a conversion operation on said data for said attribute to create reformatted data; and
storing said reformatted data for said attribute in said target instance.
11. The method of claim 9 wherein said step of comparing attributes specified in said first format with attributes specified in said second format includes comparing a first set of attribute identifiers that uniquely identify attributes in said
first format with a second set of attribute identifiers that uniquely identify attributes in said second format.
12. The method of claim 7 wherein:
the data type includes an embedded data type; and
the step of reading data that describes said first format from format data contained in said first schema version record includes reading data that describes a structure of said embedded data type.
13. A computer-readable medium carrying one or more sequences of one or more instructions for supplying data to an application, the one or more sequences of one or more instructions including instructions which, when executed by one or more
processors, cause the one or more processors to perform the steps of:
receiving a request initiated by the application for stored data to be supplied to the application;
determining a first format, said first format being the format in which said stored data is stored, and
determining a second format, said second format being the format in which said application expects to receive said stored data;
creating a target instance of said stored data by converting said stored data from said first format to said second format without said application that requested the stored data or users of the application that requested the stored data knowing
the format in which the stored data is stored; and
supplying said target instance to the application that requested the stored data.
14. The computer-readable medium of claim 13, wherein the step of determining the second format comprises the steps of:
determining a data type that corresponds to said stored data;
determining a first version identifier that identifies a version of said data type that said application uses;
searching for a first schema version record that | | |