Supporting multiple versions of a routine

• US 7,580,958 B2
• Filed: 06/17/2005
• Issued: 08/25/2009
• Est. Priority Date: 06/17/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation, ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Yang, Xiaoyu, Simanjuntak, Manogari Nogi, Miller, Robert Thomas, Yothers, Jay A., Dang, Tammie, Chen, Yao-Ching Stephen, Cotner, Curt Lee, Huang, Joe Cheng-yu, Zagelow, Margaret Alice, Cui, Baoqiu, McFeely, Claire Willey, Tsuji, Yumi Kimura
• Primary Examiner(s): BOCCIO, VINCENT F
• Application Number:
  US11/156,509
• Publication Number:
  US 20060288052A1
• Time in Patent Office: 1,530 Days
• Field of Search: 707/201, 707/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Techniques are provided for supporting versions of a routine. A first version of the routine is created. A second version of the routine is generated in response to receiving an alter statement including an add version clause. The second version of the routine is activated in response to receiving an alter statement including an activate version clause.

Claims

1. A method for supporting versions of a routine, comprising:

creating a first version of the routine in response to receiving a create statement, wherein the first version is identified as an active version in a catalog in a datastore when created in response to receiving the create statement, wherein the first version of the routine is stored in the datastore;

receiving multiple alter statements that include an add version clause;

for each of the multiple alter statements that include an add version clause that is received, creating a new version of the routine, wherein multiple versions of the routine are stored in the datastore simultaneously, wherein the catalog in the datastore identifies one version of the multiple versions as an active version of the routine, wherein the active version identifies which version of the multiple versions of the routine to call when the routine is invoked;

activating a second version of the routine in response to receiving an alter statement including an activate version clause that specifies a version to be activated, wherein the catalog in the datastore identifies the second version as the active version of the routine;

receiving a request to invoke the routine;

in response to receiving the request to invoke the routine, determining whether a version of the routine identified by a current version routine indicator exists;

in response to determining that the version identified by the current routine version indicator exists, invoking the version of the routine identified by the current version routine indicator; and

in response to determining that the version identified by the current routine version indicator does not exist, invoking the second version of the routine that is identified as the active version.

2. The method of claim 1, wherein the add version clause of an alter statement is used to create the second version with a same number and a same type of parameters as the first version.

3. The method of claim 1, wherein the multiple versions of the routine are stored with a same routine name and a same high level qualifier.

4. The method of claim 1, further comprising:

dropping a version of the routine in response to receiving an alter statement including a drop version clause.

5. The method of claim 1, further comprising:

in response to receiving a set current routine version statement, setting the current routine version indicator to override the active version and to identify another version of the routine using a current routine version clause.

6. The method of claim 1, wherein the routine comprises one of a stored procedure and a user defined function.

7. The method of claim 1, wherein the second version modifies the body of the first version, wherein the body includes statements to be executed when the second version of the routine is invoked.

8. The method of claim 1, wherein the second version modifies one or more options of the first version.

9. An article of manufacture for supporting versions of a routine, wherein the article of manufacture comprises a computer readable medium storing instructions, and wherein the article of manufacture is operable to:

create a first version of the routine in response to receiving a create statement, wherein the first version is identified as an active version in a catalog in a datastore when created in response to receiving the create statement, wherein the first version of the routine is stored in the datastore;

receive multiple alter statements that include an add version clause;

for each of the multiple alter statements that include an add version clause that is received, create a new version of the routine, wherein multiple versions of the routine are stored in the datastore simultaneously, wherein the catalog in the datastore identifies one version of the multiple versions as an active version of the routine, wherein the active version identifies which version of the multiple versions of the routine to call when the routine is invoked;

activate a second version of the routine in response to receiving an alter statement including an activate version clause that specifies a version to be activated, wherein the catalog in the datastore identifies the second version as the active version of the routine;

receive a request to invoke the routine;

in response to receiving the request to invoke the routine, determine whether a version of the routine identified by a current version routine indicator exists;

in response to determining that the version identified by the current routine version indicator exists, invoke the version of the routine identified by the current version routine indicator; and

in response to determining that the version identified by the current routine version indicator does not exist, invoke the second version of the routine that is identified as the active version.

10. The article of manufacture of claim 9, wherein the add version clause of an alter statement is used to create the second version with a same number and a same type of parameters as the first version.

11. The article of manufacture of claim 9, wherein the multiple versions of the routine are stored with a same routine name and a same high level qualifier.

12. The article of manufacture of claim 9, wherein the article of manufacture is operable to:

drop a version of the routine in response to receiving an alter statement including a drop version clause.

13. The article of manufacture of claim 9, wherein the article of manufacture is operable to:

in response to receiving a set current routine version statement, set the current routine version indicator to override the active version and to identify another version of the routine using a current routine version clause.

14. The article of manufacture of claim 9, wherein the routine comprises one of a stored procedure and a user defined function.

15. The article of manufacture of claim 9, wherein the second version modifies the body of the first version, wherein the body includes statements to be executed when the second version of the routine is invoked.

16. The article of manufacture of claim 9, wherein the second version modifies one or more options of the first version.

17. A system for supporting versions of a routine, comprising:

hardware logic capable of causing operations to be performed, the operations comprising;

creating a first version of the routine in response to receiving a create statement, wherein the first version is identified as an active version in a catalog in a datastore when created in response to receiving the create statement, wherein the first version of the routine is stored in the datastore;

receiving multiple alter statements that include an add version clause;

for each of the multiple alter statements that include an add version clause that is received, creating a new version of the routine, wherein multiple versions of the routine are stored in the datastore simultaneously, wherein the catalog in the datastore identifies one version of the multiple versions as an active version of the routine, wherein the active version identifies which version of the multiple versions of the routine to call when the routine is invoked;

activating a second version of the routine in response to receiving an alter statement including an activate version clause that specifies a version to be activated, wherein the catalog in the datastore identifies the second version as the active version of the routine;

receiving a request to invoke the routine;

in response to receiving the request to invoke the routine, determining whether a version of the routine identified by a current version routine indicator exists;

in response to determining that the version identified by the current routine version indicator exists, invoking the version of the routine identified by the current version routine indicator; and

in response to determining that the version identified by the current routine version indicator does not exist, invoking the second version of the routine that is identified as the active version.

18. The system of claim 17, wherein the add version clause of an alter statement is used to create the second version with a same number and a same type of parameters as the first version.

19. The system of claim 17, wherein the multiple versions of the routine are stored with a same routine name and a same high level qualifier.

20. The system of claim 17, wherein the operations comprise:

dropping a version of the routine in response to receiving an alter statement including a drop version clause.

21. The system of claim 17, wherein the operations comprise:

in response to receiving a set current routine version statement, setting the current routine version indicator to override the active version and to identify another version of the routine using a current routine version clause.

22. The system of claim 17, wherein the routine comprises one of a stored procedure and a user defined function.

23. The system of claim 17, wherein the second version modifies the body of the first version, wherein the body includes statements to be executed when the second version of the routine is invoked.

24. The system of claim 17, wherein the second version modifies one or more options of the first version.