Techniques for maintaining compatibility in database schemas

• US 10,031,929 B2
• Filed: 06/15/2015
• Issued: 07/24/2018
• Est. Priority Date: 11/24/2003
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Cohen, Alon, Avalani, Bhaven, Ahmed, Zahid N.
• Primary Examiner(s): Brown, Sheree
• Application Number:
  US14/739,098
• Publication Number:
  US 20150278257A1
• Time in Patent Office: 1,135 Days
• Field of Search: 707695
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A method of accommodating at least one difference between a first database schema and a second database schema is provided. The method includes receiving a request generated by an application program using a first version of a database schema, and generating a response including a reserved element that corresponds to a custom slot provided in the first version of the database schema. The method further includes communicating the response to the application program.

Claims

1. A method comprising:

receiving, via an application programming interface at a server system, a request message generated by an application program, the request message including a sub-element indicating that the application program is associated with a first version of a database schema, the request message transmitted to the server system via a network;

in response to receiving the request message including the sub-element indicating that the application program is associated with the first version of the database schema, generating, using a processor at the server system, a response message including a reserved element that corresponds to a custom slot provided in the first version of the database schema, the custom slot including a placeholder for at least one new schema element added to a second version of the database schema different from the first version of the database schema such that the reserved element is an indication that at least one new schema element is included in the second version of the database schema; and

transmitting the response message from the server system to the application program via the network.

2. The method of claim 1, wherein the first version of the database schema includes a client-side database schema, and wherein the second version of the database schema includes a server-side database schema.

3. The method of claim 1, wherein the custom slot is included in the first version of the database schema upon creating the first version of the database schema.

4. The method of claim 1, wherein the at least one new schema element is an XML schema definition and the custom slot is provided in a schema dictionary.

5. The method of claim 1, wherein the first version of the database schema is a noncurrent version, and wherein the second version of the database schema is a current version.

6. The method of claim 1, further comprising determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the second version of the database schema contains an element not found in the first version of the database schema.

7. The method of claim 1, further comprising determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the at least one new schema definition element is unrecognizable to the application program using the first version of the database schema.

8. The method of claim 7, wherein the at least one new schema definition element is unrecognizable to the application program based on the at least one new schema definition element is not included in the first version of the database schema.

9. The method of claim 1, wherein the custom slot is a placeholder.

10. The method of claim 1, further comprising determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the first version of the database schema is different than the second version of the database schema.

11. A server system comprising a computer readable non-transitory storage medium storing instructions which, in response to being executed by one or more processors of the server system, cause the server system to perform operations including:

receiving, via an application programming interface at the server system, a request generated by an application program, the request message including a sub-element indicating that the application program is associated with a first version of a database schema, the request message transmitted to the server system via a network;

in response to receiving the request message including the sub-element indicating that the application program is associated with the first version of the database schema, generating a response message including a reserved element that corresponds to a custom slot provided in the first version of the database schema, the custom slot including a placeholder for at least one new schema element added to a second version of the database schema different from the first version of the database schema such that the reserved element is an indication that at least one new schema element is included in the second version of the database schema; and

transmitting the response message from the server system to the application program via the network.

12. The server system of claim 11, wherein the custom slot is included in the first database schema upon creating the first database schema.

13. The server system of claim 11, wherein the first version of the database schema includes a client-side database schema, and wherein the second version of the database schema includes a server-side database schema.

14. The server system of claim 11, wherein the second version of the database schema is a later version of the first version of the database schema.

15. The server system of claim 11, wherein the operations further include determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the first version of the database schema has been altered.

16. The server system of claim 11, wherein the operations further include determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the at least one new schema definition element is unrecognizable to the application program using the first version of the database schema.

17. The server system of claim 16, wherein the at least one new schema definition element is unrecognizable to the application program using the first version of the database schema based on the at least one new schema definition element is not included in the first version of the database schema.

18. The server system of claim 11, wherein the operations further include determining, by comparing a schema definition for the first version of the database schema with a schema definition for the second version of the database schema, that the first version of the database schema is a non-current version of the database schema and that the second version of the database schema is a current version of the database schema.

19. A non-transitory machine-readable storage device storing instructions which, when executed by a machine, cause the machine to perform operations comprising:

receiving, via an application programming interface at a server system, a request message generated by an application program, the request message including a sub-element indicating that the application program is associated with a first version of a database schema, the request message transmitted to the server system via a network;

in response to receiving the request message including the sub-element indicating that the application program is associated with the first version of the database schema, generating a response message including a reserved element that corresponds to a custom slot provided in the first version of the database schema, the custom slot including a placeholder for at least one new schema element added to a second version of the database schema different from the first version of the database schema, such that the reserved element is an indication that at least one new schema element is included in a second version of the database schema; and

transmitting the response message from the server system to the application program via the network.

20. The machine-readable storage device of claim 19, wherein the second version of the database schema is a current version, and the first version of the database schema is a noncurrent version.