Extensible database retrieval and viewing architecture

• US 6,243,698 B1
• Filed: 12/07/1999
• Issued: 06/05/2001
• Est. Priority Date: 10/17/1997
• 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
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US09/455,839
• Time in Patent Office: 546 Days
• Field of Search: 707/10, 707/103, 707/3, 707/5, 707/1, 707/2, 707/4
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2428 Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• 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:

accessing a data access description from a storage, the data access description employing a predetermined interface defining a number of inputs and a number of outputs for use of the data description, the data access description defining an operation to be performed on the data in a series of executable steps; and

executing the data access description causing the data to be accessed from a database and manipulated according to the definition of the operation independent of operations performed by an application designed to access the database.