Method and apparatus for providing schema evolution without recompilation

• US 6,119,130 A
• Filed: 03/28/1996
• Issued: 09/12/2000
• Est. Priority Date: 03/28/1996
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation), America Online Inc. (Warner Bros. Discovery, Inc.)
• Original Assignee: Oracle Corporation
• Inventors: Krishnaswamy, Srinath, Nguyen, Tin Anh, Kotsovolos, Susan Marie
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/624,191
• Time in Patent Office: 1,629 Days
• Field of Search: 395/619, 395/500, 364/300, 340/709, 707/203, 707/100, 707/200, 707/103, 707/101
• US Class Current: 707/695
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method and apparatus that allow schema version evolution to occur without requiring applications that expect older schema versions to be recompiled is provided. According to one aspect of the invention, each application that requests data is supplied the data in the format that the application expects. To supply the data in the expected format, a mechanism is provided for tracking the evolution of data types without losing information. In addition, mechanisms are provided for determining the format expected by the application and the format in which the data is currently stored. A mechanism is also provided for converting the data from the stored format to the expected format when the two formats do not match. A data migration strategy is described in which data is gradually migrated to newer formats when the data is updated by applications that expect a more recent format than the format in which the data is currently stored.

Claims

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 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.

15. The computer-readable medium of claim 14, 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.

16. 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;

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.

17. The computer-readable medium of claim 14, wherein 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.

18. The computer-readable medium of claim 17, further comprising the step of causing said application to build said type version table upon initialization by:

causing an initialization routine within 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.

19. The computer-readable medium of claim 13, 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.

20. The computer-readable medium of claim 19, wherein said step of determining said first version identifier includes the step of reading schema version information stored with said stored data.

21. The computer-readable medium of claim 19, 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.

22. The computer-readable medium of claim 21, 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.

23. The computer-readable medium of claim 21, 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.

24. The computer-readable medium of claim 22 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.

25. A computer system for supplying data to an application, computer system comprising:

one or more processors;

a memory coupled to the one or more processors and containing one or more sequences of one or more instructions which, when executed by the 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;

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 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.

26. The computer system of claim 25, wherein the sequences of instructions for performing the step of determining the second format comprises sequences of instructions for performing 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.

27. The computer system of claim 26, wherein the sequences of instructions for performing the step of searching for a first schema version record comprises sequences of instructions for performing 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.

28. The computer system of claim 25, wherein the sequences of instructions for performing the step of determining the second format comprises sequences of instructions for performing 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.

29. The computer system of claim 26, wherein the sequences of instructions for performing the step of determining the first version identifier include sequences of instructions for performing 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.

30. The computer system of claim 29, wherein the memory further comprises sequences of instructions for causing said application to build said type version table upon initialization by:

causing an initialization routine within 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.

31. The computer system of claim 25, wherein the sequences of instructions for performing the step of determining said first format include sequences of instructions for performing 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.

32. The computer system of claim 31, wherein the sequences of instructions for performing the step of determining said first version identifier include sequences of instructions for performing the step of reading schema version information stored with said stored data.

33. The computer system of claim 25, wherein the sequences of instructions for performing the step of converting said stored data from said first format to said second format include sequences of instructions for performing 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.

34. The computer system of claim 33, wherein the sequences of instructions for performing the step of copying data for said attribute comprise sequences of instructions for performing 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.

35. The computer system of claim 33, wherein the sequences of instructions for performing the step of comparing attributes specified in said first format with attributes specified in said second format include sequences of instructions for 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.

36. The computer system of claim 31, wherein:

the data type includes an embedded data type; and

the sequences of instructions for performing the step of reading data that describes said first format from format data contained in said first schema version record include sequences of instructions for reading data that describes a structure of said embedded data type.

37. A method for supplying data to a client application in a database system, the method comprising the computer-implemented steps of:

a database server receiving a request initiated by a client application for stored data to be supplied to the client application; and

in response to the request to supply stored data to the client application, performing the steps of

determining a first format in which the stored data is stored in the database system;

determining a second format in which the client application expects to receive the stored data;

the database server causing a target instance of the stored data to be created by converting the stored data from the first format to the second format without the client application that requested the stored data or users of the client application that requested the stored data knowing the format in which the stored data is stored; and

the database server causing the target instance to be supplied to the client application that requested the stored data.

38. The method of claim 37, wherein the step of determining a second format in which the client application expects to receive the data comprises the steps of:

determining a data type that corresponds to the stored data;

determining a first version identifier that identifies a version of the data type that the client application uses;

searching for a first schema version record that corresponds to the data type;

comparing a second version identifier in the first schema version record with the first version identifier;

if the second version identifier matches the first version identifier, then the reading data that describes the second format from format data contained in the first schema version record;

if the second version identifier does not match the first version identifier, then

finding a second schema version record that is associated with the data type and which contains the first version identifier; and

reading data that describes the second format from format data contained in the second schema version record.

39. The method of claim 38, wherein the step of searching for a first schema version record comprises the steps of:

determining a type identifier that uniquely identifies the data type; and

performing a search on a plurality of schema version records based on the type identifier.

40. The method of claim 37, wherein the step of determining the second format comprises the steps of:

determining a data type that corresponds to the stored data;

determining a first version identifier that identifies a version of the data type that the application uses;

using the data type and first version identifier to locate an entry in a table; and

using information in the entry to locate a schema version record that specifies the second format.

41. The method of claim 38, wherein the step of determining the first version identifier includes the steps of:

inspecting an entry associated with the data type in a type version table associated with the application; and

reading the first version identifier from the entry.

42. The method of claim 41, further comprising the step of causing the application to build the type version table upon initialization by:

causing an initialization routine within the application to call registration routines for a plurality of libraries used by the application; and

causing the registration routines to add entries to the type version table to indicate which versions of data types are used by the plurality of libraries.

43. The method of claim 37, where in the step of determining the first format includes the steps of:

determining a data type that corresponds to the stored data;

determining a first version identifier that identifies a version of the data type that was used to store the stored data;

searching for a first schema version record that corresponds to the data type;

comparing a second version identifier in the first schema version record with the first version identifier;

if the second version identifier matches the first version identifier, then reading data that describes the first format from format data contained in the first schema version record;

if the second version identifier does not match the first version identifier, then

finding a second schema version record that is associated with the data type and which contains the first version identifier; and

reading data that describes the first format from format data contained in the first schema version record.

44. The method of claim 43, wherein the step of determining the first version identifier includes the step of reading schema version information stored with the stored data.

45. The method of claim 37, wherein the step of converting the stored data from the first format to the second format includes the step of:

comparing attributes specified in the first format with attributes specified in the second format;

if an attribute exists in the first format and the second format, then copying data for the attribute from the stored data to the target instance;

if an attribute exists in the second format but not the first format, then storing a default value for the attribute in the target instance;

if an attribute exists in the first format but not in the second format, then not copying data that corresponds to the attribute from the stored data to the target instance.

46. The method of claim 45, wherein the step of copying data for the attribute comprises the steps of:

determining whether the attribute has an identical format in the first format and the second format;

if the attribute has an identical format in the first format and the second format, then copying data for the attribute from the stored data to the target instance without performing any conversion operation; and

if the attribute does not have an identical format in the first format and the second format, then

reading data for the attribute from the stored data;

performing a conversion operation on the data for the attribute to create reformatted data; and

storing the reformatted data for the attribute in the target instance.

47. The method of claim 45, wherein the step of comparing attributes specified in the first format with attributes specified in the second format includes comparing a first set of attribute identifiers that uniquely identify attributes in the first format with a second set of attribute identifiers that uniquely identify attributes in the second format.

48. The method of claim 43 wherein:

the data type includes an embedded data type; and

the step of reading data that describes the first format from format data contained in the first schema version record includes reading data that describes a structure of the embedded data type.