Method of selecting and presenting data from a database using a query language to a user of a computer system

Abstract

A thread management system for implementation within a computer system having a database disposed to be accessed through queries provided by a system user is disclosed herein. In this environment the thread management system provides a mechanism for subsequent replication of a sequence of one or more of such queries made by the system user. In a preferred implementation, a first thread step object is generated upon a first of the queries being provided to the database. The thread step object is formed so as to include information relating to a first state of the database. A representation of the first thread step object is then presented to the system user via a display of the computer system. Upon the system user selecting the representation of the first thread step object, the first of the queries to the database is replicated. A second thread step object may be generated upon provision of a second of the queries to the database. The second thread step object is created so as to include information relating to a second state of the database. In an exemplary implementation a thread object is then formed from the first and second thread step objects, and a representation of the thread object is displayed to the system user. Upon the system user selecting the representation of the thread object, the first and second queries to the database are replicated.

Claims

What is claimed is:

1. A method of selecting and presenting data from a database using a database query language to a user of a computer system, said method comprising the steps of:

a) providing at least one frame bookmark object that specifies a format for the display of data;

b) for each of said at least one frame bookmark objects, providing a component bookmark object that specifies a criterion for data to be displayed according to the format specified by said frame bookmark object;

c) retrieving data from a database according to the a criterion specified by said component object; and

d) displaying said data according to the format specified in said at least one frame bookmark object.

2. The method of claim 1, said method further comprising the steps of:

a) dividing a screen image into a plurality of screen sectors;

b) mapping each of said frame objects to at least one of said screen sectors.

3. The method of claim 1, said method further comprising the steps of providing at least one thread object that comprises said at least one frame bookmark object.

4. The method of claim 3, said method further comprising the steps of

a) providing a thread array object that comprises said at least one thread object, and

b) presenting said user with a display of said at least one thread object, and

c) selecting said thread object in response to indicia specified by the user.

5. In a computer system having a database disposed to be accessed through queries using a database query language made to said database, a method for replicating a sequence of one or more of said queries made by a system user, said method comprising the steps of:

generating a first thread step object upon providing a first of said queries to said database, said thread step object including information relating to a first state of said database;

displaying a representation of said first thread step object upon a display of said computer system; and

replicating said first of said queries to said database upon selection by said user of said representation of said first thread step object.

6. The method of claim 5 further including the steps of:

generating a second thread step object upon providing a second of said queries to said database, said second thread step object including information relating to a second state of said database, and

forming a thread object from said first and second thread step objects.

7. The method of claim 6 further including the steps of:

displaying a representation of said thread object, and

replicating said first and said second of said queries to said database upon selection by said user of said representation of said thread object.

8. In a computer system having a database disposed to be accessed through queries using a database query language made to said database, a system for replicating a sequence of one or more of said queries made by a system user, said system comprising:

means for generating a first thread step object upon providing a first of said queries to said database, said thread step object including information relating to a first state of said database;

means for displaying a representation of said first thread step object upon a display of said computer system; and

means for replicating said first of said queries to said database upon selection by said user of said representation of said first thread step object.

9. The system of claim 8 further including:

means for generating a second thread step object upon providing a second of said queries to said database, said second thread step object including information relating to a second state of said database, and

means for forming a thread object from said first and second thread step objects.

10. The system of claim 9 further including:

means for displaying a representation of said thread object, and

means for replicating said first and said second of said queries to said database upon selection by said user of said representation of said thread object.

Description

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

INTRODUCTION

1. Technical Field

This invention relates to a system and method for interacting with a computer system database, and, more particularly, for providing a representation of such interaction to system users.

2. Background

Many computer programs endeavor to present data to users in ways that are convenient for the user to specify, and that do not require overly complex programming to tailor for a specific application. In this regard, some computer programs function to record information relating to previously viewed data so as to permit a user to subsequently recall a selected portion of the previously viewed data.

For example, a number of commercially available programs include a history logging facility to record recently viewed data. Specifically, the word processing program MICROSOFT WORD.TM. maintains a "recently used file list." This is a list of an arbitrary number of the files that have been most recently edited using MICROSOFT WORD.TM.. The list is saved between invocations of Word, and is optionally displayed as a series of menu items on a menu displayed to the user. The menu items correspond to the names of the files. If a user desires to edit one of the files listed, the user may select the file name. MICROSOFT WORD.TM. responds as though the user had entered the full file name in response to an "Open File" dialog, thereby permitting the user to resume editing the file. Although the recently used file list is useful for recalling a specific file for further editing, its role is limited to that of obtaining the file and applying formatting and other information stored within the file. No contextual information about how the file was displayed is retained. That is, when a file is loaded from the recently used file list, contextual information such as indication of a particular page that was being viewed by the user in the previous session, a previous cursor location, etc. and the like is not also replicated by the loading process.

In database environments, it would be particularly advantageous to provide a contextually complete production of a previously-displayed screen of data. Although numerous database products offer the capability to store database queries for future repeated execution, these products require affirmative efforts on the part of the user to store the query. Moreover, with most stored query-based database systems, not all contextual information is reproduced for the user upon subsequent execution of the stored query. For example, if a stored query is retrieved and reexecuted, the system generally displays the data beginning with the first record, even if in a previous session the user had scrolled through several records before storing the query.

Accordingly, it would be desirable to provide a means of recording a history of queries made to a database without requiring intervention on the part of a user to store a query. It would be further desirable to provide a means to group together data displays that are closely related, for example, data displays that are the result of a user's requests to see successively more detailed portion of a particular view of a database. It would be further desirable to provide a means to display a summary of the stored queries so as to allow selection of a desired query from the list of stored queries.

SUMMARY OF THE INVENTION

The thread management system of the present invention may be implemented within a computer system having a database disposed to be accessed through queries provided by a system user. In this environment the inventive thread management system provides a mechanism for subsequent replication of a sequence of one or more of such queries made by the system user. In a preferred implementation, a first thread step object is generated upon a first of the queries being provided to the database. The thread step object is formed so as to include information relating to a first state of the database. A representation of the first thread step object is then presented to the system user via a display of the computer system. Upon the system user selecting the representation of the first thread step object, the first of the queries to the database is replicated.

In another aspect of the present invention, a second thread step object is generated upon provision of a second of the queries to the database. The second thread step object is created so as to include information relating to a second state of the database. A thread object is then formed from the first and second thread step objects, and a representation of the thread object is displayed to the system user. Upon the system user selecting the representation of the thread object, the first and second queries to the database are replicated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an computer system in which may be implemented the thread management system of the present invention.

FIG. 2 depicts a screen to displayed following submission of a query to a database of the computer system of FIG. 1.

FIG. 3 depicts a Screen View Object defined by the thread management system of the present invention.

FIG. 4 depicts a Frame Object of the inventive thread management system.

FIG. 5 depicts a Business Component Object of the inventive thread management system.

FIG. 6 depicts a Thread Array Object of the thread management system of the present invention.

FIG. 7 depicts a Thread Object of the inventive thread management system.

FIG. 8 depicts a Thread Step Object of the thread management system of the present invention.

FIG. 9 depicts a Screen Bookmark Object of the thread management system of the present invention.

FIG. 10 depicts a Frame Bookmark Object of the inventive thread management system.

FIG. 11 depicts a Business Component Bookmark Object defined by the thread management system of the present invention.

FIG. 12 depicts the creation of a Thread Array Object in accordance with the invention.

FIG. 13A is a flow chart representative of the creation of a first Thread Object.

FIG. 13B illustratively represents the various program entities responsible for execution of the program steps shown in FIG. 13A.

FIG. 14A is a flowchart depicting the steps performed during the creation of a Thread Step.

FIG. 14B represents the interrelationships among the various routines involved in the creation of a Thread Step Object 84.

FIG. 15 depicts the screen representation resulting from the steps performed in FIG. 14.

FIG. 16 is a flow chart representative of the creation of a Thread Object other than a first Thread Object.

FIG. 17 is a flow chart representative of the steps involved in the restoration of a Thread Step.

FIG. 18 depicts an exemplary sequence of steps to be performed in restoration of a previously saved thread.

FIG. 19 shows a display of a set of names stored in various Frame Objects.

FIG. 20 depicts steps that may be taken at program termination to store a Thread Array on a disk or other persistent storage.

DESCRIPTION OF SPECIFIC EMBODIMENTS

Introduction and Definitions

The invention relates to a system and method for facilitating the storage and retrieval of database queries performed by a user. A query is an interaction of the user with the database program by which the user requests a portion of the database to be retrieved and displayed. The exact form of the query is not material to the operation of the invention. Any query that is supported by the relational database employed by the invention may be used. Typically, queries may be queries expressed according to a well-known standard such as Structured Query Language (SQL) or Query By Example (QBE). A query may be either independent or dependent. An independent query is a query that is not related to a previously executed query. A dependent query is a query that is defined by selecting data that has been displayed in response to a previously executed query.

In accordance with the invention, an object (i.e., a "thread object") is created when certain independent queries are requested by the user. A thread object represents a series (or "thread") of queries that are initiated as a result of certain independent queries. A thread object is comprised of one or more "thread step objects." Each thread step object represents a query (a "thread step") that is initiated by the user. Thread objects, and its constituent thread step objects, are maintained and stored so as to permit recall of a thread and its constituent thread steps. This advantageously allows recall and reexecution of previously stored queries.

When a user submits an independent query, a thread is begun with a single step that represents the independent query. A user may then request a dependent query by selecting portions of the data displayed on the screen. When the user requests a dependent query, a thread step representing the dependent query is added to the thread. The resulting thread is then stored upon the performance of one of various predefined events. For example, the thread may be stored upon entry of a new independent query, or upon exit from the program.

In one aspect of the invention, a chronological list is displayed of all the threads initiated by the user and stored in system memory. When a desired one of the displayed threads is then selected using conventional pointer (e.g., point and click) operations, the selected thread is recalled and the one of its thread steps corresponding to the most recent dependent query of the thread is then executed.

After the thread step corresponding to the independent query of a thread has been so executed, the user is further provided with a list of the remaining thread steps corresponding to the dependent queries of the thread. The user may then optionally select one these remaining thread steps, at which time the dependent query associated with the selected remaining step is executed. Alternately, the user may submit additional queries, which are then added to the thread.

By facilitating the storage and retrieval of sequences of one or more previously executed queries, the present invention thus facilitates convenient subsequent reexecution of such previously executed queries.

It is contemplated that the thread management system of the invention be implemented in an object-oriented computer system. As used herein, the term "object" refers to an integrated collection of data and functions that describe an entity or business function, as well as the operations capable of being performed on or by the entity or business function. Functions and data contained within an object may be designated as either private or public. Private functions and data may be referenced only by the object in which they are contained. In contrast, private functions and data may be referenced by any object. Objects can also access databases, and serve as interfaces to non-object-oriented subsystems.

A "class" serves as a template that describes the types of data necessary to describe a member of the class, but does not include data that describes any particular member of a class. An object describes a particular member, or "instance" of a class. When an object is created and initialized with data to represent a member, it is said to be "instantiated." For example, a class named EMPLOYEE may specify that an employee has a first name and a last name, a hire date, a salary, etc. When an object of the class EMPLOYEE is instantiated, memory storage is allocated to hold the information and functions for a particular employee. Once an object is instantiated, the data that describes the class member represented by the object can be referenced and manipulated.

Although the present invention is described herein with reference to the C++ language and the Microsoft Foundation Class (MFC) Library, it is understood that any computer language (object-oriented or otherwise) may be used without departing from the spirit or scope of the invention.

In addition, the present invention is described herein by using, by way of example, a relational database comprised of information concerning a salesperson's various leads and opportunities. However, it is understood that the invention may be used with relational databases designed to include other types of subject matter.

System Overview and Screen Displays

FIG. 1 depicts an computer system in which may be implemented the thread management system of the present invention. Computer system 10 is a general purpose computer capable of executing a computer program in accordance with the thread management system of the present invention. Computer system 10 includes a base unit 12 containing a CPU and disk drive (not shown), a keyboard 14 and a pointing device such as mouse 16. The results of operations performed by the computer may be displayed on monitor screen 18 of monitor 20.

FIG. 2 depicts a screen 30 that may be displayed following a user's submission of a query. Screen 30 includes a number of Frames 32. In the example depicted, Screen 30 includes an Opportunity Frame 32a, a Contacts Frame 32b, an Activities Frame 32c and a Notes Frame 32d.

A Frame 32 may be either a list frame or a form frame. A form frame is a frame that displays a single record of data in detailed form in two dimensions. Opportunity Frame 32a is an example of a form frame. A form frame comprises a series of fields 34 that are arrayed in two dimensions, and that contain information about a single record in a database. A particular field 34 of a form frame may be designated as a Key Field 35. The contents of key field of a form frame may be used to provide criteria relating to selection of data to be displayed in one or more list frames. In the exemplary display of FIG. 2, the field labeled "Opportunity" serves as a key field 35.

A list frame is a frame used to display a selected number of records of a database as a series of rows 36. For example, a list frame may display data relating to a row selected by the Key Field 35 of a Form Frame. Each row is displayed in a single dimension, generally the horizontal dimension. In FIG. 2, Contacts Frame 32b is an example of a list frame. Contacts Frame 32b displays a series of rows 36. Each row 36 is displayed horizontally and contains multiple fields 38 corresponding to database fields as specified by the criteria of Key Field 35. In the exemplary display of FIG. 2, Contacts Frame 32b contains only contacts having values for the "Opportunity" field which are equal to the value in Key Field 35.

In FIG. 2, Activities Frame 32c is also a list frame. However, Activities Frame 32c is seen to lack any data entries. This indicates that there exist no Activity records having "Opportunity" fields equal to the value of Key Field 35. Likewise, Notes Frame 32d is also a list frame lacking any data. This indicates that there are not any Notes records in existence having "Opportunity" fields equal to the value of Key Field 35.

As will be more fully described herein, screen 30 further displays a series of Tab Icons 40 capable of being used to initiate threads. As will also be described in further detail, screen 30 additionally includes a Thread Bar 42 and a Thread Array Icon 44 disposed to retrieve and reexecute previously performed queries.

The appearance of the Screen Image 30, including the size and selection of Frames 32, is typically specified in an external screen definition file. The operation of such a screen definition file is not material to the present invention, and will not be further described.

Current Display Objects

FIGS. 3 through 5 depict objects which are jointly representative of the form and content of data presented in a Screen 32. These objects may be collectively referred to as "Current Display Objects." Current Display Objects include the Screen View Object, the Frame Object, and the Business Component Object.

FIG. 3 depicts a Screen View Object 60. Screen View Object 60 is used to hold data descriptive of the state of the screen image currently being displayed as Screen 30. More particularly, Screen View Object 60 comprises a Screen View Object Header 62, and an array of Frame Objects 64. The Screen View Object Header 62 includes Screen Query Name 61 and Screen Name 63. Screen Query Name 61 contains the name of the stored query which led to creation of the Screen 30 represented by Screen View Object 60. Queries may be physically stored by computer system 10 using conventional techniques, and hence the particulars of such techniques will not be further discussed.

Screen Name 63 is a name assigned to the Screen 30. Typically, Screen Name 63 is a composite of a character string that identifies a Form Frame within the Screen 30, and the value contained in the Key Field 35. For example, for the Screen View Object 60 representing the Screen 30 depicted in FIG. 2, the associated Screen Name 63 may be the string "Oppty:Telesales Lan at Best".

The public data portion of Screen View Object 60 may be represented with the following C++/MFC program code, in which CString and CObArray are MFC classes:

    ______________________________________
    public:
    CString    m.sub.-- queryName;
                            // name of query
    CString    m.sub.-- viewName;
                            // name assigned screen
    CObArray   m.sub.-- frameArray;
                            // array of frame objects
    ______________________________________

    ______________________________________
    public:
    CString     m.sub.-- activeFieldName;
                              // name of active field
    CString     m.sub.-- frameName;
                              // name of frame
    CSSBusComp* m.sub.-- pBusComp;
                              // pointer to Business
                               Object
    ______________________________________

    ______________________________________
    public:
    CString m.sub.-- busCompName
                          // name of business object
    CString m.sub.-- busQuery
                          // query used to retrieve data
    Cstring m.sub.-- sortSpec
                          // specification of sort order
    CString m.sub.-- selRowId
                          // Number of current row displayed
    ______________________________________

    ______________________________________
    public:
    CObArray    m.sub.-- threadArray;
                             // array of thread objects
    ______________________________________

    ______________________________________
    public:
    CObArray    m.sub.-- stepArray;
                            // array of thread step objects
    ______________________________________

    __________________________________________________________________________
    public
    CString     m.sub.-- fieldValue
                           // thread step field value
    CString     m.sub.-- title
                           // thread step title
    CSSViewBookmark*
                m.sub.-- pViewBookmark;
                           // pointer to Screen BookMark
    __________________________________________________________________________

    __________________________________________________________________________
    public
    CString m.sub.-- currentQueryName;
                         // storage for query name
    Cstring m.sub.-- viewName;
                         // storage for screen name
    CString m.sub.-- activeFrameName;
                         // storage for active frame name
    CobArray
            m.sub.-- frameBookmarkArray;
                         // array of Frame Bookmarks
    __________________________________________________________________________

    __________________________________________________________________________
    public:
    CString    m.sub.-- activeFrameName;
                          // storage for active frame name
    CString    m.sub.-- activeFieldName
                          // storage for active field name
    CSSBCBookmark*
               m.sub.-- pBCBookmark;
                          // pointer to business component
                          // bookmark
    __________________________________________________________________________

    ______________________________________
    public:
    CString m.sub.-- CompName;
                         // name of business object
    CString m.sub.-- Query;
                         // query used to retrieve data
    CString m.sub.-- sortSpec;
                         // specification of sort order
    Cstring m.sub.-- selRowId;
                         // Number of current row displayed
    ______________________________________

• Inventors
  Ambrose, Jesse Lee; Rothwein, Thomas Michael;
• Assignee
  Siebel Systems, Inc. (San Mateo, CA)
• Published
  Feb-3-1998
• Current US Classes:
  705/1
  707/103R
  707/104.1
  715/501.1
• Application #
  535553
• International Classes
  G06F 017/30
• Field of Search
  395/614 395/201 395/762
• Examiner
  Black; Thomas G.
• Agent
  Cooley Godward LLP
• US Patent References:
  5566330
  5572643
  5581758
  5630125