Accessing single entities in OData entity sets

Patent metadata

Field	Value
Publication number	US-9959310-B2
Application number	US-201414318898-A
Country	US
Kind code	B2
Filing date	Jun 30, 2014
Priority date	Nov 25, 2013
Publication date	May 1, 2018
Grant date	May 1, 2018

Abstract

A system includes activation of an OData service exposing a parameterized database view, the OData service exposing a Parameter Entity Type and a Result Entity Type, wherein the Parameter Entity Type specifies one or more input parameters of the database view as properties of the Parameter Entity Type, and defines a Parameter Entity Type key formed by each of the one or more input parameters, and wherein the Result Entity Type specifies the one or more input parameters and one or more output of the database view as properties of the Result Entity Type, and defines a Result Entity Type key formed by each of the one or more input parameters and at least one of the one or more output parameters. Also included is reception of an OData request comprising a Uniform Resource Indicator, the Uniform Resource Indicator including the OData service, the Result Entity Type, and a value for each of one or more input parameters of the database view and for at least one of the one or more output parameters of the database view, and execution, in response to the request, of the OData service to return a single entity associated with the values.

First claim

What is claimed is:

1. A system comprising:
a database storing data; and
a processor to execute processor-executable process steps to cause the system to:
activate an OData service by creating an OData service definition for the OData service, the OData service definition specifying a database view, the OData service definition including generation of a Parameter Entity Type and a Result Entity Type, wherein the Parameter Entity Type specifies one or more input parameters of the database view as properties of the Parameter Entity Type, the OData service definition defining a Parameter Entity Type key formed from each of the one or more input parameters, and wherein the Result Entity Type specifies the one or more input parameters and one or more output of the database view as properties of the Result Entity Type, and the OData service definition defining a Result Entity Type key formed from each of the one or more input parameters and at least one of the one or more output parameters;
receive an OData request comprising a Uniform Resource Indicator, the Uniform Resource Indicator including the OData service, the Result Entity Type, and a value for each of one or more input parameters of the database view and for at least one of the one or more output parameters of the database view; and
in response to the request, execute the OData service to return a single entity associated with the values.

2. The system according to claim 1 , wherein execution of the OData service comprises:
execution of an OData handler to construct database statements based on a metadata definition of the OData service, and to invoke the database statements using a Structured Query Language Application Programming Interface.

3. The system according to claim 1 , the processor to further execute processor-executable process steps to cause the system to:
receive a second OData request comprising a second Uniform Resource Indicator, the second Uniform Resource Indicator including the OData service, the Parameter Entity Type, a value for each of one or more input parameters of the database view, and a filter value of at least one of the one or more output parameters of the database view; and
in response to the second request, execute the OData service to return a list comprising a single entry associated with the values.

4. The system according to claim 3 , the processor to further execute processor-executable process steps to cause the system to:
receive a third OData request comprising a second Uniform Resource Indicator, the third Uniform Resource Indicator including the OData service, the Parameter Entity Type, and a value for each of one or more input parameters of the database view; and
in response to the third request, execute the OData service to return a set of all entities of the database view which are associated with the values.

5. The system according to claim 1 , the processor to further execute processor-executable process steps to cause the system to:
receive a second OData request comprising a second Uniform Resource Indicator, the second Uniform Resource Indicator including the OData service, the Parameter Entity Type, and a value for each of one or more input parameters of the database view; and
in response to the second request, execute the OData service to return a set of all entities of the database view which are associated with the values.

6. A computer-implemented method comprising:
activating an OData service by creating an OData service definition for the OData service, the OData service definition specifying a database view, the OData service definition including generation of a Parameter Entity Type and a Result Entity Type, wherein the Parameter Entity Type specifies one or more input parameters of the database view as properties of the Parameter Entity Type, the OData service definition defining a Parameter Entity Type key formed from each of the one or more input parameters, and wherein the Result Entity Type specifies the one or more input parameters and one or more output of the database view as properties of the Result Entity Type, and the OData service definition defining a Result Entity Type key formed from each of the one or more input parameters and at least one of the one or more output parameters;
receiving an OData request comprising a Uniform Resource Indicator, the Uniform Resource Indicator including the OData service, the Result Entity Type, and a value for each of one or more input parameters of the database view and for at least one of the one or more output parameters of the database view; and
in response to the request, executing the OData service to return a single entity associated with the values.

7. The computer-implemented method according to claim 6 , wherein executing the OData service comprises:
executing an OData handler to construct database statements based on a metadata definition of the OData service, and to invoke the database statements using a Structured Query Language Application Programming Interface.

8. The computer-implemented method according to claim 6 , further comprising:
receiving a second OData request comprising a second Uniform Resource Indicator, the second Uniform Resource Indicator including the OData service, the Parameter Entity Type, a value for each of one or more input parameters of the database view, and a filter value of at least one of the one or more output parameters of the database view; and
in response to the second request, executing the OData service to return a list comprising a single entry associated with the values.

9. The computer-implemented method according to claim 8 , further comprising:
receiving a third OData request comprising a second Uniform Resource Indicator, the third Uniform Resource Indicator including the OData service, the Parameter Entity Type, and a value for each of one or more input parameters of the database view; and
in response to the third request, executing the OData service to return a set of all entities of the database view which are associated with the values.

10. The computer-implemented method according to claim 6 , further comprising:
receiving a second OData request comprising a second Uniform Resource Indicator, the second Uniform Resource Indicator including the OData service, the Parameter Entity Type, and a value for each of one or more input parameters of the database view; and
in response to the second request, executing the OData service to return a set of all entities of the database view which are associated with the values.

11. A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause to the computer system to:
activate an OData service by creating an OData service definition for the OData service, the OData service definition specifying a database view, the OData service definition including generation of a Parameter Entity Type and a Result Entity Type, wherein the Parameter Entity Type specifies one or more input parameters of the database view as properties of the Parameter Entity Type, the OData service definition defining a Parameter Entity Type key formed from each of the one or more input parameters, and wherein the Result Entity Type specifies the one or more input parameters and one or more output of the database view as properties of the Result Entity Type, and the OData service definition defining a Result Entity Type key formed from each of the one or more input parameters and at least one of the one or more output parameters;
receive an OData request comprising a Uniform Resource Indicator, the Uniform Resource Indicator including the OData service, the Result Entity Type, and a value for ea

Assignees

• Foebel Florian
• Friedmann Bjoern
• Gruschko Boris
• Mohr Christian
• Strenge Martin
• Zorn Sascha
• Sap Se

Inventors

• Foebel Florian
• Friedmann Bjoern
• Gruschko Boris
• Mohr Christian
• Strenge Martin
• Zorn Sascha

Classifications

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F16/215

  Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors · CPC title

• G06F16/2365 Primary

  Ensuring data consistency and integrity · CPC title

• H04L63/083

  using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title

• G06F16/21

  Design, administration or maintenance of databases · CPC title