KR20020063967A - Query Window System - Google Patents

Abstract

PURPOSE: A query language window system is provided to save window resources and make an input/output of the query language possible in a CRT terminal by receiving a query language related window in an operator in an operator instruction input window directly and outputting the window through an output window without creating a query language related window additionally and to make a top/down instruction input possible by supplying a query language related exclusive graphic window. CONSTITUTION: A control mode(100) controls interactive operations of modules in a system and a data flow. A query language input/output module(110) receives a query language processing instruction from a user, displays a processing result, and supplies a query language window graphic interface. A query language processing module(120) analyzes query language stream information inputted through the query language input/output module(110) adapted to a format, reconstructs query language information, performs a sentence structure analysis and a data access to a database(200) using the reconstructed data, and transmits a processing result to the input/output module(110).

Description

Query Window System

The present invention relates to a query window system of an electronic switching system supporting an improved query usage environment, input / output format, and multi-port function.

In the conventional query window, when an open command (for example, 'OPEN_QRY) is entered in an operator command window, a database query group block (abbreviated as DBQG) block and MC (window manager and command analysis), The block is linked to create an INPUT window and an OUTPUT window separately.

The query related to the database is input on the newly created INPUT window, and the processing result is output through the OUTPUT window.

In this case, overlapping with the CONSOLE window or the OUTPUT window that is driven for input and output of the existing operator command occurs, the messages to be output to each window are output or broken into the wrong window.

In addition, when inputting a general operator command other than a query word, the query window must be iconized or closed. Also, a query computer cannot be used in an input port of the CRT type. Done.

When entering a structured query language (SQL) statement in the query input window, it is difficult to use the long sentence in accordance with the syntax and syntax, as well as to accurately input the system configuration information.

On the other hand, since the query window is a text window, its appearance is out of date, and window management is cumbersome to specify all formats one by one.

In addition, when a plurality of PCs simultaneously run and use a query window, each port is not managed individually, resulting in a mixed input / output message between terminals.

The present invention was devised to solve these problems. When using a query in an operator command input window, the window resource can be directly output from the operator command input window and output through the output window without separately generating a query related window. The purpose of the present invention is to provide a query window system that enables query input / output in a CRT terminal and provides a graphic window related to the query, enabling top-down command input.

In addition, it is another object of the present invention to configure a query system to allow only one type of query word to be input at the same port through port-by-port management so that input / output information is not mixed even when query words are simultaneously input from a plurality of ports.

1 is a block diagram showing the configuration of a query window system according to a preferred embodiment of the present invention.

2 is an exemplary diagram illustrating a graphic interface of an input / output window provided by a query input / output module.

<Description of the symbols for the main parts of the drawings>

100: control unit (control module) 110: query input / output module

111: relation name input module 112: access command input module

113: processor input module 114: optional input module

115: relation information output module 116: domain information output module

117: query command output module 118: clear module

119: sequential search module 120: query processing module

121: Query processing result output window 200: Database

In order to achieve the above object, the present invention provides a query input / output module for receiving a query from a user and displaying a processing result and providing a query window interface in a query window system of an ATM switch including a database, and a query input / output module. After analyzing the query stream information input through the / output module according to the format, reconstructing the query information, performing parsing and data access to the database using the reconstructed data, and transmitting the processing result to the input / output module. The query processing module controls the interaction and data flow of each module, and displays the query input / output module in the user command input window instead of generating a query related window separately when using the query in the user command input window. I / O It is characterized in that a control module to perform.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

In addition, it should be noted that the same reference numerals are given to the same components, although belonging to different drawings for convenience of understanding.

1 is a block diagram showing the configuration of a query window system according to a preferred embodiment of the present invention.

As shown, the query window system is composed of a control module (control unit 100) center that controls the interaction and data flow of the modules in the system.

The query input / output module 110 receives a query processing command from a user, displays a processing result, and provides a query window graphic interface.

The query processing module 120 analyzes the query stream information input through the query input / output module 110 according to a format, reconstructs the query information, and parses the data using the reconstructed data and the data to the database 200. Performs an access and transmits the processing result to the input / output module 110.

2 is an exemplary diagram illustrating a graphic interface of an input / output window provided by a query input / output module.

The query input / output module 110 is composed of sub-modules 111 to 119, which will be described with reference to FIGS. 1 and 2.

The relation name input module 111 receives a relation name or relation ID to perform a query.

In this case, the relation name desired by the user may be directly input, or may be input through a combo box.

The relation name stored in the combo box is stored in memory and provided through the selection window.

Preferably, the relation name or ID is input only when the first process is executed, and the relation name or ID received at this time is stored in the memory and then received through the combo box.

The access command input module 112 selects and receives an access command for the selected relation.

Preferably, direct text entry is not possible and allows the combo box to display a list of commands and select the required access command. At this time, selectable database query commands include SELECT, UPDATE, INSERT, DELETE, MAXL, MINL, SUM, COUNT, AVG (average).

The processor input module 113 receives a processor that performs a query on the relation.

The option input module 114 is a function that is performed when SELECT and UPDATE are selected in the access command. The option input module 114 may select IN SEQ and IN ORDER during SELECT and DSKBK and MEMUP during UPDATE.

RELATION INFORMATION The information output module 115 outputs information on the selected relation. Examples include relation ID, relation type (MEM, DKO, DKB, PROJ, JOIN), relation location type (NOR, DIS, REP, LOR, PDIS), processor on which relation is implemented, global access processor, Outputs the key domain and search method (seq, index, bin, hash), etc.

The domain information information output module 116 outputs the domain information when the relation is selected and the cursor point is located in the domain input edit box after the domain of the relation is output. The output domain information is domain name, domain size, domain type and the like.

The query output module 117 outputs a query when selecting an access command through the access command input module and outputs condition completion when selecting a database query command for condition input.

When the condition input is completed and the condition completion button is clicked, the selected database query command is output through the query processing result output window 121.

The clear module 118 performs the function of clearing the information of the query processing result output window 121 that has already been outputted when the user wants to start again from the beginning while proceeding to execute the database query command.

Preferably, the clear module performs its function in the form of a clear button as shown in FIG. 2.

The sequential search module 119 is similar to the function of IN SEQ in the above-described option button. When performing a sequential search sequentially, it is preferable to search the next tuples sequentially after selecting once and to have a next button (NEXT BUTTON) form. Do.

As described above, through the window interface provided by the query input / output module 110, the user inputs a condition corresponding to the query command, and then executes the command by clicking the button changed to the access command. It is output through the query processing result output window 121 located at the edit box or the bottom. If abnormally performed, the abnormal result or reason is output.

Preferably, when the user inputs an open command (eg, OPEN-QRY) in the user input window to open the query window, the query window does not run separately, and the operator input window itself enters the query word. Switch to the query window via the graphical interface provided to the output module 110.

Also, the QRY> prompt can be used to indicate that the query window is in the query mode. The return key recognizes the end of the query syntax line input.

If the command 'OUIT;' is entered, the query window mode is terminated and the screen returns to the operator input window.

On the other hand, in the existing CRT terminal, it is impossible to run a separate query window, so it is impossible to use a query. However, by using an operator command window with a query window, the query can be used in a CRT terminal. The query usage is the same as the query usage using the operator command window described above.

When the control module 100 receives a request for using a query, the control module 100 merely drives a process for managing query input / output information without separately requesting an input window and an output window.

In addition, the control module 100 allows separate management for each port of each process so that only one type of query can be input to one port so that information is not compromised even when query words are simultaneously input from multiple ports. It is desirable to prevent input and output information from being mixed even if query words are simultaneously input from the user.

Although the preferred embodiments of the present invention have been described in detail above, those skilled in the art will appreciate that the present invention may be modified without departing from the spirit and scope of the invention as defined in the appended claims. It will be appreciated that modifications or variations may be made. Therefore, changes in the future embodiments of the present invention will not be able to escape the technology of the present invention.

As described above, according to the present invention, when a query is used in an operator command input window, the query command input window is directly input from the operator command input window without separately generating a query related window through an interface provided by the query input / output module. It is possible to save the window resources by outputting, to query I / O in the CRT terminal, and to provide a query window system that enables the top-down command input by providing a dedicated graphic window related to the query.

In addition, through port-by-port management, only one type of query is allowed in the same port, so that input and output information is not mixed even when query words are simultaneously input from a plurality of ports.

Claims (5)

In the query window system of an ATM switch including a database, A query input / output module that receives a query processing command from a user, displays a query processing result, and provides a query window graphic interface; After analyzing the query stream information input through the query input / output module, reconstruct the input query information, and perform query syntax analysis and data access to the database using the reconstructed data. A query processing module for transmitting a processing result of the query module to the input / output module; When a user inputs an open command (eg, OPEN-QRY) in a user input window to open a query window, the query window is not driven separately, but the operator input window itself is converted to the query window. Controls the interoperability and data flow of the modules, and when a query open command is input from the user, the query is displayed by displaying the query input / output module on the command input window of the user without generating a separate query input and output window. Query window system comprising a control module for performing input and output processing of the. The method of claim 1, wherein the query input / output module, A relation name input module configured to receive one of a relation name and a relation ID to perform a query; An access command input module for receiving an access command for the input relation; A processor input module configured to receive a processor that performs a query on the input relation; A relation information information output module configured to output information of the selected relation; A domain information output module for outputting domain information by the domain of the selected relation; A jill output module for outputting a query processing result transmitted from the query processing module; The method of claim 2, wherein the query input / output module further includes a clear module that performs a function of clearing the already outputted query processing information when the user proceeds to perform the input query and starts from the beginning again. Query window system, characterized in that. The query window system of claim 2, wherein the domain information output through the domain information output module is at least one of a domain name, a domain size, and a domain type. The query window system of claim 1, wherein the control module separately manages ports of each query processing process and allows only one type of query word to be input to one port.