Method and apparatus for validating and configuring database transaction requests from multiple clients

• US 20050165776A1
• Filed: 01/14/2004
• Published: 07/28/2005
• Est. Priority Date: 01/14/2004
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: F. Morgan, Fabian, Phillips, Brent Russel, Marappan, Kumar, Focazio, Robyn Lee
• Granted Patent: US 7,299,234 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

The present invention provides a method, computer program product, and a data processing system for validating and configuring a database transaction request. A first transaction criteria of a plurality of transaction criteria is identified in a singleton in-memory object by reading a client identifier element value specified in a database transaction request. Each of the plurality of transaction criteria is associated with a respective client. Default data for a database path is determined based on the client identifier element value. A database command is generated that includes the default data.

Claims

1. A method for validating and configuring a database transaction request, the method comprising the computer implemented steps of:

identifying a first transaction criteria of a plurality of transaction criteria in a singleton in-memory object by reading a client identifier element value specified in a database transaction request, wherein each of the plurality of transaction criteria is associated with a respective client;

determining default data for a database path based on the client identifier element value; and

generating a database command including the default data.

2. The method of claim 1, wherein the database transaction request is included in an extensible markup language document.

3. The method of claim 1, wherein the step of determining includes:

determining the transaction request does not specify data for the database path.

4. The method of claim 3, further including:

evaluating a required element of the first transaction criteria; and

responsive to evaluating the required element, determining the database transaction request is not required to specify data for the database path.

5. The method of claim 1, wherein the database command is a structured query language command.

6. The method of claim 1, including:

identifying a second transaction criteria by reading a client identifier element value specified in a second database transaction request; and

determining the second database transaction request does not include data for a database path specified in the second transaction criteria.

9. The method of claim 1, wherein the default data is specified in the first transaction criteria.

7. The method of claim 7, including:

evaluating a required element of the second transaction criteria; and

generating an error.

8. The method of claim 7, wherein the required element indicates the second database transaction request is required to include data for the database path specified in the second transaction criteria.

10. A computer program product in a computer readable medium for validating a database transaction request, the computer program product comprising:

first instructions for reading transaction request element values including a client identifier element value from a database transaction request; and

second instructions for identifying a first transaction criteria of a plurality of transaction criteria of a singleton in-memory object based on the client identifier element value, responsive to determining data for a database path specified in the first transaction criteria is not included by the transaction request element values, generating a database command including default data for the database path.

11. The computer program product of claim 10, wherein the database transaction request is an extensible markup language document.

12. The computer program product of claim 10, wherein the first instructions are an extensible markup language parser.

13. The computer program product of claim 10, wherein the database command is a structured query language command.

14. The computer program product of claim 10, wherein the default data is specified by the first transaction criteria.

15. A data processing system for validating database transaction requests, comprising:

a memory that contains a set of instructions and a singleton in-memory object; and

a processing unit, responsive to execution of the set of instructions, for reading element values including a client identifier element value of a database transaction request and identifying a transaction criteria of the singleton in-memory object based on the client identifier element value, wherein default data is identified for the database transaction request in response to determining data for a database path is not provided in the transaction request, the processing unit generating a database command including the default data.

16. The data processing system of claim 15, further comprising a network adapter for receiving the database transaction request.

17. The data processing system according to claim 15, wherein the default data is specified by the transaction criteria.

18. The data processing system according to claim 15, wherein the processing unit, responsive to reading a client identifier element value of a second database transaction request, generates an error.

19. The data processing system of claim 18, wherein the processing unit generates the error upon determining that data for a database path is not specified in the second transaction request and a transaction criteria identified by the client identifier element value of the second database transaction request specifies data for the database path is required.

20. The data processing system of claim 15, wherein a plurality of transaction criteria are identified based on the client identifier element value.