Database view systems

• US 8,881,036 B2
• Filed: 06/13/2012
• Issued: 11/04/2014
• Est. Priority Date: 06/13/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kemmler, Andreas, Kamenz, Torsten
• Primary Examiner(s): TITCOMB, WILLIAM D
• Application Number:
  US13/495,324
• Publication Number:
  US 20130339881A1
• Time in Patent Office: 874 Days
• Field of Search: 715/762, 715/757
• US Class Current: 715/762
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: H04L 12/00 Data switching networks interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00
• CPC Class Codes: H04L 12/6418 Hybrid transport

Abstract

Embodiments of methods and systems for database viewing, create a copy of a vendor view in a customer view layer that is present between an interface layer and the database layer. In certain embodiments this copy of the vendor view may contain no customer specific logic, simply serving as a 1:1 projection in the customer view allowing the vendor to track customer access to particular vendor views. According to some embodiments, the copy of the vendor view may be changed to create a modification view. Changes are applied to the modification view only, leaving the original vendor view unchanged with a link to the stored modification copy. This link can be used to adjust the modification copy whenever a hot fix or a new version of the ‘modified’ database content is installed to the customer system. Embodiments may support consumer extensions to the vendor views and/or to the database itself.

Claims

1. A computer-implemented method comprising:

providing a database layer comprising a database table and a vendor view thereto;

causing a view engine to create a customer view based upon the vendor view in a customer view layer between the database layer and a user interface layer;

storing a first link between the customer view and the vendor view;

communicating to a database content vendor, stored tracking information regarding the first link;

causing the view engine to implement a change in a copy of the vendor view to create a modification view; and

causing the view engine to create a second link between the modification view and the vendor view, wherein the vendor view comprises a customer extension, and the copy includes the customer extension.

2. A method as in claim 1 wherein the view engine is caused to implement the change by a database vendor during an upgrade process.

3. A method as in claim 1 wherein the stored tracking information comprises a popularity of customer access to the first link.

4. A method as in claim 1 wherein the customer view is based upon a database table not referenced by the vendor view.

5. A non-transitory computer readable storage medium embodying a computer program for performing a method, said method comprising:

providing a database layer comprising a database table and a vendor view thereto;

causing a view engine to create a customer view based upon the vendor view in a customer view layer between the database layer and a user interface layer;

storing a first link between the customer view and the vendor view;

communicating to a database content vendor, stored tracking information regarding the first link;

causing the view engine to implement a change in a copy of the vendor view to create a modification view; and

causing the view engine to create a second link between the modification view and the vendor view, wherein the vendor view comprises a customer extension, and the copy includes the customer extension.

6. A non-transitory computer readable storage medium as in claim 5 wherein the view engine is caused to implement the change by a database vendor during an upgrade process.

7. A non-transitory computer readable storage medium as in claim 5 wherein the stored tracking information comprises a popularity of customer access to the first link.

8. A non-transitory computer readable storage medium as in claim 5 wherein the customer view is based upon a database table not referenced by the vendor view.

9. A computer system comprising:

one or more hardware processors;

a software program, executable on a hardware processor of said computer system, the software program configured to;

access a database layer comprising a database table and a vendor view thereto;

cause a view engine to create a customer view based upon the vendor view in a customer view layer between the database layer and a user interface layer;

store a link between the customer view and the vendor view;

communicate to a database content vendor, stored tracking information regarding the first link;

cause the view engine to implement a change in a copy of the vendor view to create a modification view; and

cause the view engine to create a second link between the modification view and the vendor view, wherein the vendor view comprises a customer extension, and the copy includes the customer extension.

10. A computer system as in claim 9 wherein the stored tracking information comprises a popularity of customer access to the first link.

11. A computer system as in claim 9 wherein the customer view is based upon a database table not referenced by the vendor view.