Abstract:
A method, system and program for providing a graphical interface for a database are accomplished by the operation of a process in the memory of a processor. A selected entry in the database is dynamically used as input to a conditional definition dialog box. The definition of individual conditions, the definition of the relationship of conditions to the selected entries, the editing of conditions, and the editing of the relationship of conditions is simplified and rendered dynamic and interactive for the user thereby facilitating the completion of the task being performed. The user need not remember the related column information for a specified predicate because the system will provide that information simultaneously with the conditional definition in a form that supports the direct manipulation of the related information. The selected entries and their relationship are displayed simultaneously with the definition activities for both the initial definition and any subsequent editing activities. The user may select this information and drag it to the desired location to proceed on the desired activity.

Description:
This is a continuation of application Ser. No. 07/916,240 filed Jul. 20, 1992, abandoned. 
    
    
     FIELD OF THE INVENTION 
     This invention generally relates to improvements in database queries and more particularly to a graphical display for creating database queries of row conditions. 
     BACKGROUND OF THE INVENTION 
     Databases have become the subject of significant recent interest, not only because of the increasing volume of data being stored and retrieved by computerized databases but also by virtue of the data relationships which can be established during the storage and retrieval processes. 
     Structured Query Language (SQL), and in particular ANSI SQL, has become a preferred language media for communicating queries to relational databases. As a consequence, there presently exist thousands of relational databases and thousands of related queries directed to such databases. Given an investment in such databases and queries, migration is not only a desirable feature, but a substantially necessary capability for new relational database systems and methods. 
     The concept of portraying a query in a graphical depiction on a display screen of a workstation is a relatively new approach to relational database interfacing. Visual queries, often referred to as graphical queries, utilize workstation graphics to represent query objectives heretofore defined by SQL statements. A visual query presents a pictorial depiction of the objectives of a search, thereby eliminating any need for a user to learn a query language, improving the rate at which SQL queries can be formulated, and reducing the defect or error rate of queries. 
     With the growing prevalence of relational databases, communication networks and workstations, the training and experience of a representative system user has decreased in relation to the resources available. The dilemma created by these various events is threefold. First, there exists an established and valuable base of queries formulated with classical SQL expressions. Second, there is a growing usage of relational databases and networks accessing their information. The end users of such databases are routinely less proficient in the very tools needed to efficiently and accurately access the relational database information. Finally, users of database access methods do not receive direct feedback of changes based on their manipulation of the database. Thus, a distinct need exists for methods, systems and programs which convert query statements into visual representations understandable by novice database users, and, in the compliment, which convert graphically or visually represented queries into SQL format statements usable in existing databases and network environments. 
     An article by Faloutos, F., and Sellis, T., entitled, &#34;An Efficient Pictorial Database System for PSQL&#34;, IEEE Transactions on Software Engineering, Vol. 14, No. 5, May 1988, discusses a prior art technique for searching a K or B-tree database using efficient data structures for optimizing the search. The report discusses access techniques for retrieving information and displaying the information on graphical displays. For example, demographic information can be used to retrieve information and format it graphically to reflect population in various sections of the United States. An improvement to further optimize the access of data for subsequent graphic display is disclosed in U.S. Pat. No. 4,905,163 and IBM Technical Disclosure Bulletin Vol. 30, No. 1, June 1987, Intelligent Scheduling, Query and Reporting Data Base. 
     An example of a dynamic, graphical display for a knowledge base application is found in U.S. Pat. No. 4,752,889 to Neuron Data. The patent discloses a graphical tree structure depiction of a knowledge base that is updated after changes are made to the database via user line commands. 
     In the prior art, there are various programs that allow users to define row conditions during the definition of a database query. For example, users have access to programs for defining queries that include the SQL WHERE clause. This input is a text string in a separate panel, or a string in the flow of the entire query command text. Users may enter the command language text in either form. This text requires user access to the keyboard, or other alphanumeric entry device. 
     All known current approaches have at least two problems. First, the row condition definition is not initialized with any information regarding the target column. Second, the text string is a keyboard only action that excludes the overwhelming trend in user interfaces to direct manipulation by means of a pointing device and selection. 
     The impact of these problems with current implementations is that extra time is required for users to define row conditions. The absence of the related column information causes delays and errors because human memory is relied upon to replicate information that is already known to the system. The user must switch from pointing device to keyboard and then back which introduces errors and delays. The current approaches do not aid the user in the performance of the action desired; i.e., the definition of the row conditions to achieve a desired subset of database records. 
     SUMMARY OF THE INVENTION 
     Accordingly, it is a primary object of the present invention to provide a unique method and system for the visual presentation of row database information using a graphical display and provide row condition definition using the graphical display. 
     According to the invention, the definition of row conditions, and the editing of row conditions is simplified and rendered dynamic and interactive for the user thereby facilitating the completion of the task being performed. The user need not remember the related column information for a specified condition because the system will provide that information simultaneously with the initialization of the condition definition in a form that supports the direct manipulation of the related information. The condition is displayed simultaneously with the definition activities for both the initial definition and any subsequent editing activities. The user may grab this information and drag it to the desired location to proceed on the desired activity. 
     The benefits of the invention include enhanced user performance on the row condition task by having direct manipulation of the related column information during the task. The user is also supported for direct manipulation of the sub-tasks that comprise the row condition definition task. The user is not required to memorize information that can be provided by the system. This makes the system easier to use by both novice and experienced users, and no matter what the skill level of the user, errors are reduced as a result of the graphical interface which provides only the valid operations for selected objects. 
     These and other objects of the present invention are accomplished by the operation of an algorithm in the memory of a processor. The processor accesses data structures to determine the current status of a database and displays the logical relationships of the information stored in the database graphically. A user employs a pointing device to select and change portions of the database and its logical relationships via the graphic user interface. The selection and changes are dynamically applied to the relational database via modifications to the underlying data structures and reflected graphically on the display. Additional, dynamic data structures, called presentation objects are created based on user created information defining relationships, new tables, groups, constraints, row conditions, having conditions, SQL statements, categories and sets of existing database information. The dynamic data structures can ultimately become part of the original database. The method, system and program is comprehensive in dynamic creation of data structures called presentation objects for use in the direct manipulation and change of a database. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1a is a block diagram of a personal computer system in accordance with the subject invention; 
     FIG. 1b schematically depicts a workstation connected to a network with a relational database in accordance with the subject invention; 
     FIG. 2 is an illustration of visual query displays in accordance with the subject invention; 
     FIGS. 3 and 4 are detailed flowcharts in accordance with the subject invention; and 
     FIG. 5 is the detailed logic for committing the dialog box selections in accordance with the subject invention. 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     Queries which obtain information from relational databases are conventionally defined with ANSI standard Structure Query Language (SQL) statements. These statements define in computer recognizable terms the tables from which the data is to be extracted, the columns of interest, the conditions rows must satisfy, what columns are to be included, how the select columns are to be grouped, the order of the columns, distinctiveness constraints in the columns, connections of data within tables, and lower level or subqueries to be integrated into the base queries. A simple text describing SQL and its uses appears in the IBM Operating Systems/2 Extended Edition Database Manager Structured Query Language (SQL) Concepts booklet published by IBM Corporation in 1991. In addition to the ANSI standard SQL statements, there exist a number of nonstandard SQL statements within the relational database community. Thus, any bidirectional translation resource must have the diversity of structure to interface a broad spectrum of relational database SQL language variances. 
     As noted earlier, comprehensive bidirectionality of the translation is important from the perspective of migrating from established SQL queries to their graphical or visual query equivalents. It is inefficient to require the regeneration of existing SQL queries into the visual environment. At the same time, new visual queries should be available in SQL format for use on existing hardware with existing relational databases. Comprehensive bidirectionality and direct manipulation via a graphical display is lacking in the prior art. 
     Some technologies do exist for providing very limited translation from SQL to a visual or graphical depiction. Representative examples are described in &#34;Graphical User Languages for Querying Information: Where to look for criteria?&#34; by Hrohr, as published in 1988 IEEE Workshop On Visual Languages, May 1988, pages 14-20; &#34;Design and Implementation of An Interactive Graphical Query Interface for a Relational Database Management System&#34; by Czejdo et al, as appeared in 1988 IEEE Workshop On Visual Languages, May 1988 pages 21-28; and &#34;End-User Access to Relational Databases Metaphor Database Server&#34; by Benjamin et al, as appeared in the summer 1987 issue of InfoDB. 
     Unfortunately, the translations described in such publications were lacking both in comprehensive bidirectionality and scope of diversity. Namely, the focus was only directed toward translating from SQL to visual or graphical depictions. Furthermore, the translations were not ANSI standard SQL comprehensive, in that the row condition was incapable of handling diverse logical relationships, no mathematical relationships were permitted for column data, and subquery handling was absent. None of the teachings even remotely suggested the ability to directly manipulate a database directly from the graphic display. The article &#34;User Interfaces for Structural Engineering Relational Database&#34; by Howard et al as appeared in Engineering With Computers, 1988, pages 239-249, recognized the importance of bidirectional translation between a text based query, the defined Engineering Query Language and graphical representations. However the article did not disclose how such desirable objectives could be accomplished. The article recognized the potential need for translating relatively complex query formulations and applying them directly from a graphical interface to a database, but made no attempt to present a solution. In contrast, the present invention defines a method, system and program for accomplishing these desirable goals and doing so with the resources to handle complex formulations, including, but not limited to, the definition of complex logical and algebraic relationships between columns and the manipulation of hierarchical queries composed of subqueries. 
     The invention is preferably practiced in the context of a relational database such as is available in the OS/2 Extended Edition software program available from IBM Corporation. A representative hardware environment is depicted in FIG. 1a, which illustrates a typical hardware configuration of a workstation in accordance with the subject invention having a central processing unit 10, such as a conventional microprocessor, and a number of other units interconnected via a system bus 12. The workstation shown in FIG. 1a includes a Random Access Memory (RAM) 14, Read Only Memory (ROM) 16, an I/O adapter 18 for connecting peripheral devices such as disk units 20 to the bus, a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/or other user interface devices such as a touch screen device (not shown) to the bus, a communications adapter 34 for connecting the workstation to a data processing network and a display adapter 36 for connecting the bus to a display device 38. 
     A network of workstations, including an IBM brand PS/2 workstation, is illustrated in FIG. 1b, having resident thereon the OS/2 Extended Edition base operating system and the aforementioned OS/2 Extended Edition relational database program. Workstation 39 includes nonvolatile storage for the database, such as a hard disk, optical disk or tape drive media, and means for communicating into a network, generally at 40, having attached thereto further databases 41 and 42 as well as distinct non-proximate workstations such as 43. The fundamental goal is to provide a relatively inexperienced relational database user of workstation 39 with a method, system and program resources to create, modify and execute relational database queries encompassing a broad and historical base of information. The invention further contemplates that preexisting queries formulated in classical SQL format be conveyed to workstation 39 and subjected to conversion into visual or graphical queries equivalent for display on a graphic display 44. The user thereafter refines the query, executes the query and dynamically views the results on the graphic display. 
     A basic tenet of the user interface architecture for Structured Query Language (SQL) queries is that unlike the computer with it&#39;s mathematical language and rigid parsing rules, humans use categories to organize information and understand relationships between objects. An object is any actual entry in a relational database. The information necessary for the computer to perform a query of a relational database using SQL is visually structured into related objects with the text representing the objects of interest and the graphical representation of these objects depicting the relationships that exist or are of interest to the requester. The reader is referred to IBM&#39;s SQL REFERENCE, SC26-4380 pl (1989) for a detailed description of statements in the Structured Query Language (SQL). These statements include create, alter, and drop objects; retrieve, insert, update, and delete data in them; and grant and revoke privileges over them. The publication gives a complete description of all SQL elements and an alphabetic list of all SQL statements implemented by IBM, with descriptions of their syntax, options, and effects. 
     In defining the row condition (Where condition) for a SQL query, the user usually needs to specify a set of conditions (predicates) as building blocks of the row condition. Each predicate involves column(s) comparison. More likely, the column comparison is comparing a column against a value, another column, or a column expression. The present invention provides a method that exploits this special characteristic to reduce the complexity in defining a predicate for the row condition. 
     FIG. 2 shows a user interface design of Visual Query. The Staff 210 and ORG 220 are windows of tables referenced in a SQL query definition. The contents of each table window is the list of columns, such as 240 in table window Staff 210, belonging to the table. The user can double click a column entry in a table window to define a predicate based on the clicked column. When a column entry is double clicked, a dialog box, such as the Condition Definition dialog box 230 shown in FIG. 2, will be displayed for defining a predicate against the column. As the dialog box is displayed initially, the full name (TableName.ColumnName) of the clicked column is automatically transferred into the entry field of Label. For example, when column SALARY 211 is double clicked, the dialog box 230 will be displayed with the text &#34;Staff.SALARY&#34; in the entry field 231 for Label definition 232. A complete predicate is composed of three parts: the left side (Label), the Comparison Operator, and the right side (a value or a subselect statement for nesting subqueries). The interface of the present invention will automatically fill in the Label, so the user does not need to type in the name of the column for comparison. The possible comparison operators are listed in a scrollable list box 233. 
     The user can use a pointing device to select the appropriate operator without using the keyboard. In addition, if the right side is another column or a subquery, this user interface also allows the user to enter the appropriate information by direct manipulation techniques, such as dragging a column name to the entry field 235 for Value 237 or a subquery icon (if available) to the Subquery field 238. 
     The present invention can provide automatic input of the initial information for defining a predicate against a column. This automatic, dynamic information exchange can facilitate the process for defining a predicate and reduce the possibility of user errors. ##SPC1## 
     FLOWCHARTS IN ACCORDANCE WITH THE SUBJECT INVENTION 
     FIGS. 3, 4 and 5 are flowcharts in accordance with the subject invention. Processing commences at function block 300 of FIG. 3 where a column entry is selected. Then, at function block 310, a dialog box is presented to prompt a user for predicate definitions based on the selected column entry. Control is then returned to the calling program at terminal 320. FIG. 4 completes the processing commencing with function block 400 which displays the dialog box for defining a predicate. The dialog box is as shown at label 230 of FIG. 2. After the dialog box is displayed at function block 400, the name of the selected column entry is obtained as shown in function block 410, and the name of the selected column entry is displayed in accordance with function block 420 and illustrated at label 231 of FIG. 2. Then, at function block 430, the user selections in the dialog box are processed and control is returned to the calling program at terminal 440. 
     FIG. 5 is the detailed logic for committing the dialog box selections in accordance with the subject invention. At function block 500, a dialog box commit is initiated based on a user selection. Then, at function block 510, the corresponding data values from the dialog box are copied to the data structure used by ROW CONDITION. Then, at function block 520, the predicate object contents are built based on the ROW CONDITION data structure and the predicate is displayed in the ROW CONDITION window at function block 530 and control is returned to the calling program at terminal 540. 
     While the invention has been described in terms of a preferred embodiment in a specific system environment, those skilled in the art recognize that the invention can be practiced, with modification, in other and different hardware and software environments within the spirit and scope of the appended claims.