Extensible database retrieval and viewing architecture

• US 6,038,558 A
• Filed: 10/17/1997
• Issued: 03/14/2000
• Est. Priority Date: 10/18/1996
• Status: Expired due to Term

• Current Assignee: Group 1 Software Inc. (Böwe Systec AG)
• Original Assignee: Sagent Technology, Inc. (Böwe Systec AG)
• Inventors: Powers, Craig R., Gorelik, Vladimir
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/953,392
• Time in Patent Office: 879 Days
• Field of Search: 707/1, 707/2, 707/4, 395/676
• US Class Current: 1/1
• CPC Class Codes: G06F 16/242 Query formulation
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

One embodiment of the invention includes an architecture for extending the data requesting and data viewing capabilities of a database system. Data from the database is requested and viewed using a plan. The plan defines the steps to perform to request and view the data. The extensible architecture allows for the relatively easy addition of new steps for use in the database retrieval and viewing system. In one system, each step includes executable code for accessing, manipulating and/or outputting data. Each step conforms to a predefined interface that allows the step to be used in a plan, manipulate data received from another step (if necessary), and output data to another step (if necessary). By generating steps that conform to the predefined interface, developers can extend the functionality of the data retrieval and viewing application. In one embodiment, the interface defines the type of step, the number of inputs and outputs to the steps, the type of record accessing characteristics are best used by the step, and whether the step uses the original records or copies of the records. Importantly, the interface does not need to define the actual data manipulation performed by the step. Therefore, the step'"'"'s internal operations are independent of the operations performed by the application. This separation allows developers to generate powerful steps without having to modify the application to support the new steps.

Claims

1. A method of accessing data in a data source using a computer system:

receiving a selection of a series of steps to be performed in accessing the data, each step in the series of steps including a type, a definition of the inputs and outputs, a definition of data accessing characteristics for the step, and an indication of whether original data or copies of the data are used in the step;

receiving a selection of interconnections among the series of steps to create a plan, the plan defining the execution order of the series of steps; and

executing the plan to access the data.

2. The method of claim 1 wherein each step in the series of steps defines at least one of a source of data, a data transform or a sink of data.

3. The method of claim 2 wherein a step in the series of steps defines a source of data as being a table and column in a database management system.

4. The method of claim 2 wherein a step in the series of steps defines a data transform for converting from a first currency to a second currency.

5. The method of claim 2 wherein a step in the series of steps defines a data sink as a table to be displayed in an application window.

6. The method of claim 1 wherein a step in the series of steps is associated with an executable program code to manipulate data when the step is used in the plan.

7. The method of claim 6 wherein the executable program code includes a dynamic linked library.

8. The method of claim 1 wherein each step in the series of steps has a common interface for presenting at least the corresponding type and definition of inputs and outputs.

9. The method of claim 8 wherein the common interface also defines whether a single pass or multiple passes are used in processing that data for the corresponding step.

10. The method of claim 8 wherein the common interface conforms to the Microsoft Common Object Model (COM) interface.

11. A system for accessing and presenting data, the system comprising:

a database management system for accessing and storing source data;

a computer, being coupled in communications with the database management system, having,

a repository including a plurality of steps, each step in the plurality of steps including a type, a definition of the corresponding inputs and outputs, a definition of data accessing characteristics for the step, and an indication of whether original data or copies of the data are used in the step, and

a store having a plurality of programs corresponding to the plurality of steps, each program in the plurality of programs for manipulating the data;

an application, coupled in communication with the repository and the store, for data retrieval and viewing using the repository and the store to retrieve, manipulate and present the data in the database management system.

12. The system of claim 11 wherein each step in the plurality of steps is represented by a step object, wherein each step object provides a common interface, and wherein the application accesses the common interface to determine at least the corresponding type, inputs and outputs, and data accessing characteristics.

13. The system of claim 12 wherein the type of step is one of an input step, a transform step, or an output step.

14. The system of claim 12 wherein at least one step in the plurality of steps defines an interface for prompting a user for information to be provided to the application.

15. The system of claim 11 further comprising an on-line transaction processing system for storing source data, the database management system being coupled in communications with the on-line transaction processing system.

16. A system for accessing data in a data source using a computer system:

means for receiving a selection of a series of steps to be performed in accessing the data, each step in the series of steps including a type, a definition of the inputs and outputs, a definition of data accessing characteristics for the step, and an indication of whether original data or copies of the data are used in the step;

means for receiving a selection of interconnections among the series of steps to create a plan, the plan defining the execution order of the series of steps; and

means for executing the plan to access the data.

17. The system of claim 16 wherein each step in the series of steps defines at least one of a source of data, a data transform or a sink of data.

18. The system of claim 16 wherein a step in the series of steps defines a source of data as being a table and column in a database management system.