WO2015041575A1

WO2015041575A1 - Method for generating syntactically and semantically correct commands

Info

Publication number: WO2015041575A1
Application number: PCT/RU2014/000703
Authority: WO
Inventors: Сергей Михайлович НАЗАРОВ
Original assignee: Сергей Михайлович НАЗАРОВ
Priority date: 2013-09-23
Filing date: 2014-09-23
Publication date: 2015-03-26

Abstract

The invention is based on the generation of syntactically and semantically correct commands, and consists in: converting Backus-Naur text form, which comprises a meta-description of a command which is to be converted, into a Backus-Naur relational form comprising a meta-description of the command mentioned, which meta-description is recognizable by a database management system; converting a text semantic rule, which comprises restrictions governing the execution of the command mentioned into a relational semantic rule comprising the restrictions governing the execution of the command mentioned, which restrictions are recognizable by the database management system; identifying the command mentioned; designating the basic semantic rule for the identified command, wherein the basic semantic rule includes at least one relational semantic rule; forming a resulting dynamic structure for the identified command; identifying elements of the basic semantic rule, which elements are present in the resulting dynamic structure; applying all of the elements of all of the relational semantic rules present in the basic semantic rule mentioned, which is present in the resulting dynamic structure, to the identified command; generating a syntactically and semantically correct command on the basis of all of the elements of all of the relational semantic rules applied to the identified command.

Description

METHOD FOR GENERATING SYNTACTICALLY AND SEMANTICALLY TRUE COMMANDS

Technical field

The invention relates to solutions in the field of database management systems (DBMS), in particular to a method for generating syntactically and semantically correct instructions.

State of the art

The Backus-Naur (BNF) forms are widely known from the prior art for describing the syntax of programming languages, in particular the SQL (Structured Query Language), which is used to build queries to databases (DB) (see, for example, URL: http: / / docs. oracle. com / cd / E 11882 01 /server.112/e41084/ap_syntx002.htm#i63160 8) -

The Oracle DBMS commands for managing a database instance are described in Diana Lorentz et al. "Oracle Database SQL Language Reference)), llg Release 1 (11.1), August 2010 (URL: http://docs.oracle.com/cd/B28359_01/server.11 l / b28286.pdf).

All Oracle DBMS commands are elements of the SQL language developed by Oracle. To describe the syntax of SQL commands, syntax diagrams (SD) and a simplified version of the BNF are used. Command systems in other Oracle products, for example, PL / SQL, Backup and Recovery, Expdp, Impdp, can also be described using BNF.

In addition to Oracle DBMS, there are other examples of DBMS, for the description of the command system which versions of the BNF are used. An example of such a DBMS is Microsoft SQL Server (URL: http: //msdn.nucrosoft.corn/enus/library/msl77563%28v=sql.90%29.aspx).

From the above it follows that BNF are widely used as a means of describing the syntax of command systems of modern DBMSs. Moreover, the functionality of modern DBMS is such that the number of unique commands with all possible options for their construction is several million operators. To work with such a large number of commands (queries), automated procedures for generating the commands necessary for the user are necessary.

The closest analogue of the claimed technical solution is the technical solution described in patent US 5812840 A, G06F 17/30, SPEEDWARE Ltee./Ltd., 09/22/1998. This document describes a method for interactively constructing a syntactically and semantically correct query for a relational database based on a user’s choice, while the database has many tables, each of the tables has many columns and has a predetermined relationship with the other tables mentioned. This method is based on the interactive interaction of the user and the program and does not provide a high degree of accuracy, automation of the process of forming syntactically and semantically correct commands. In addition, in this technical solution, there is no implementation of an automatic method for generating a relational description of command syntax based on a meta-description of command syntax, which allows reducing the amount of computation necessary to form a syntactically and semantically correct request.

Disclosure of invention

The aim of the present invention is the provision of a method, device and system for the automatic generation of syntactically and semantically correct instructions, providing the generation of syntactically and semantically correct instructions with a high degree of accuracy and automation.

The technical result is to provide automation and improve the accuracy of generating DBMS commands and reduce the amount of computation required to generate DBMS commands.

Embodiments of the present invention relate to methods, devices, and systems for generating syntactically and semantically correct instructions for executing successive stages in which in a preferred embodiment of the present invention is carried out:

a) converting at least one Backus-Naur text form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, into at least one Backus-Naur relational form containing recognized by the database management system (DBMS) meta-description of the command to be converted into a syntactically and semantically correct command;

b) converting at least one text-based semantic rule containing at least one restriction on the execution of a command to be converted into a syntactically and semantically correct command into at least one relational semantic rule containing at least , one recognized DBMS restriction on the execution of a command to be converted into a syntactically and semantically correct command;

c) identification of at least one command to be converted to a syntactically and semantically correct command;

d) designating at least a basic semantic rule for an identified instruction to be converted to a syntactically and semantically correct instruction, the basic semantic rule including at least one relational semantic rule;

e) the formation of the resulting dynamic structure for the identified team to be converted into a syntactically and semantically correct command;

f) the identification of the elements of the mentioned basic semantic rule for the identified command to be converted into syntactically and semantically correct command contained in the resulting dynamic structure formed for an identified command to be converted to a syntactically and semantically correct command;

g) applying all the elements of all relational semantic rules contained in the at least one basic semantic rule contained in the resulting dynamic structure generated for the identified command to be converted to a syntactically and semantically correct command to the identified command to be converted to syntactically and semantically correct command;

h) the generation of a syntactically and semantically correct command based on all elements of all relational semantic rules applied to the identified command to be converted into a syntactically and semantically correct command from the at least one basic semantic rule contained in the resulting dynamic structure generated for an identified command to be converted to a syntactically and semantically correct command.

Despite the fact that in an exemplary embodiment of the invention, the listed computer instructions are written in PL / SQL, it should not be considered that this embodiment of the invention limits the writing of the listed computer instructions only to this programming language. In fact, the listed commands can be written in any well-known or newly created programming language.

Brief Description of the Drawings

In FIG. 1 illustrates the main steps of a method for generating syntactically and semantically correct instructions.

In FIG. 2 illustrates an exemplary embodiment of a computing device suitable for implementing a method for generating syntactically and semantically correct instructions. In FIG. 3 illustrates an exemplary embodiment of a system suitable for implementing a method for generating syntactically and semantically correct instructions.

Embodiments of the invention

The possible implementations of the embodiments of the present invention described in this section are presented as an example of creating a create table syntax to describe a CREATE TABLE command, which is an Oracle DBMS control command. A method, device, or system can be applied to any command to control any DBMS or query any DBMS, which can be described using the BNF metalanguage and to which semantic rules can be applied. For a more detailed and detailed disclosure of the actions performed by the method, it is necessary to consider the properties of the BPF in more detail.

The BNF metalanguage is the standard language for describing the syntax of programming languages.

A simplified version of the BPF includes the following symbols and conventions:

“[” And “]” are brackets that limit optional elements;

"{" And "}" are braces that limit only one item;

"|" - a vertical bar separating alternatives inside brackets or curly braces (separator);

“...” is an ellipsis indicating that the syntax element in front of it can be repeated (sign of repeatability);

“Delimiters” are delimiters that differ from brackets, braces, vertical bars and ellipses, which must be entered as shown.

Further, structural elements (SE) are understood as pairs of corresponding brackets "{", "}" and "[", "]". SE and the vertical bar "|" are auxiliary. They are not elements of the programming language that is described using the BNF metalanguage. In addition to SE, the meta-description of the programming language includes terminal elements (TE) and non-terminal elements (NTE). TEs, or keywords, are described in bold and uppercase. NTEs are described in lower case and are replaced by a name or value during the generation of commands. The need for such a record is due to the functioning of the DBMS, which recognizes commands based on the form of their record - the syntax. Commands written in violation of the requirements set forth in the documentation for the DBMS will not be recognized and processed by the DBMS. This is due to the fact that when processing DBMS commands, the commands will be translated into machine code, which will be processed by the DBMS processor. In the event that the syntax of commands written in a high-level language is violated, such commands will accordingly be translated into incorrect machine code, which will not be processed by the DBMS processor. Further, under the elements (EL) are meant TE or NTE, or a separator.

For the purposes of a more complete disclosure of the present invention, it is necessary to consider such a BNF element as a cell.

A cell is a subset of BNF of one level of nesting, limited by FE or vertical bar. The symbol "...." inside the cell denotes any valid BNF. In addition, there are also degenerate cells, inside which there is no EL, and there is only SE. In the case of a degenerate cell, two external SCs do not contain any EL, only SC, and the third SC contains EL.

For the purposes of a more complete disclosure of the present invention, it is necessary to consider such a phenomenon as the level of nesting (HC).

The first HC (HC1) corresponds to EL and SE and represents the level of the SQL command, the generation of which is carried out in accordance with the present invention. The content of SE in turn refers to

b the second HC (HC2). EL “AAAA”, “bbbb”, “dddd” and the separator “|” corresponds to UV2. The EL of the next embedded SE, namely the EL “SSSS”, “xxxx” and “|”, corresponds to the third HC (UVZ). EL "ΥΥΥΥ" corresponds to the fourth HC (UEZD). UV1 corresponds to degenerate cellular, since there is no SC at this level.

The following cells are located on HC2:

Cell 1, bounded by the FE "{" and "|";

Cell 2, bounded by the SE “|” and “}”.

The following cells are located at UVZ:

Cell 3 bounded by "[" and "|";

Cell 4, limited to "|" and "]".

On UV4 there is the following cell:

Cell 5, limited - "{" and "}".

In this example, the SEs “{”, “}” and “[”, “]” are interchangeable.

Further, for the purpose of more fully disclosing the present invention, it is necessary to consider relational BNF (rBNF).

In the present invention, RBNFs are used as elements of an automated system to generate the entire set of syntactically correct DBMS control commands and are contained in the basic semantic rule assigned to a command to be converted to a syntactically and semantically correct command. However, only the syntactically correct command will not execute the DBMS correctly. In addition to the correct command syntax, it is also necessary to apply the correct semantic rules to such a command. Semantic rules include refinements and exceptions that are used in processing the corresponding commands. These semantic rules should also be formalized (translated into a relational form), their application should be automated to ensure the generation of syntactically and semantically correct instructions.

When implementing the method of the present invention occurs conversion of text BNF to relational BNF. With such a conversion, all FE and all EL that were previously contained in text BPFs are saved. Nesting of the BNF SE is represented by hierarchical relationships between the records of the relational table, in the form of which the RBNF is presented. The start and end of the SE are represented by links between the corresponding entries in the table. Cells of one HC are represented by a unidirectional list of all SCs for each HC separately. These SEs for rbnf are:

opening elements (OE): "{" or "[", or "|"; and

closing elements (WE): "}" or "]", or "|".

For the sign of repeatability, a separate attribute (column) is generated in the RBNF. For a repeating SC, this attribute is assigned a non-empty value.

The process of converting text BNF to RBNF includes the steps of:

aa) identification of the BNF, which identifies the text BNF to be converted into rBNF, and each element of the text BNF (each record of the text BNF) is assigned a unique identifier

(ID);

bb) the formation of an intermediate table containing all the elements of the text BNF;

cc) dividing elements of the intermediate table into separate SE, TE, NTE, separators and signs of repeatability;

dd) the formation of the resulting elements of the final table containing many records, each of which contains only one received element;

her) the identification of all MA and SE and the generation of links (links) between the corresponding MA and GE;

ff) the generation of hierarchical links (links) for all nested SEs, and the generation of hierarchical links is carried out as the way that the embedded SE refers to the SE inside which it is located;

gg) identification of all signs of repeatability;

hh) assignment to all SCs located in front of the sign of repeatability of a sign of repeatability other than identified and the removal of all previously identified signs of repeatability, with the exception of newly assigned;

ii) forming a unidirectional list of cells.

At the stage of converting textual BNF to rBNF, all SE and EL contained in the textual BNF are identified. In this specific non-limitative example, ELs are CREATE, GLOBAL, TEMPORARY, TABLE, schema., Table, relational_table, object_table, XMLType_table limited by the corresponding SE - "[" and "]" for "GLOBAL" and "TEMPORARY", other "[" and "]" for "schema.", "{" And "}" for nested alternative EL "relational_table", "object_table" , "XMLType_table" and delimiters "|" for them. Column U contains a unique record identifier (EL), column FILE_NAME contains the name of the converted BNF, column LINE contains the element BNF (record BNF), column NXT contains a link to the closing structure bracket for the opening structure bracket, and a link to the opening structure bracket parenthesis, the PREV column contains a link to the external SE or 0 for the most external SE, the NREF column contains a link to the previous cell restriction. If the FE is repeating, the corresponding cell in the DEEP column is assigned the value 1. In addition, each RBNF has a unique key, each element of which can be associated with a corresponding element of unique keys of relational semantic rules (RSF), which will be described in detail below.

In general terms, the RBNF contains the following attributes: RBNF name - the name of a particular team or a fragment of the DBMS documentation (the name of the text BNF);

rBNF body - a formalized entry of text BNF;

rBNF unique key - any unique key that can be formed from one or more entries contained in the rbnf.

In particular, such a key can be a key formed from the line number (GO), the name rBNF (text BNF) and the record in one of the cells rBNF. For example, a unique key may be a combination of records from columns P) and FILE NAME and LINE located on the same row.

When performing the procedure for generating syntactically and semantically correct commands, the following actions can be performed on RBNF:

for optional SCs (SCs enclosed in brackets “[” and “]”), a pass may be applicable, while such SCs may be removed from the RBNF; for a SC that is repeating (a SC recorded before the sign of repeatability “...”), duplication can be applied, creating a copy of such a SC and recording it after the initial SC; for EL, a choice can be applied, while the cell in which the EL is written is determined to be selected, and the SE in which the cell is located is replaced by the selected cell, and the selected cell goes to a higher HC;

for an STE, which is an RBNF, the substitution of an STE with an RBNF body can be applied;

for an STE that is not a BPF, a value assignment procedure may be applied;

if rSP are defined for EL, then the procedure for deriving all rSP can be applied to such EL, accompanied by an indication of the result of each rSP;

for EL, the procedure for outputting a DBMS documentation fragment that relates to such EL can be applied; Yu Based on the list of ELs located on HC1, an SQL command can be generated.

In more detail, the process of generating syntactically and semantically correct SQL commands can be represented as a loop:

aaa) at UV1, NTEs that are the names of the BPF are selected;

bbb) selected NTEs are replaced by the corresponding BNF bodies;

ccc) if there is an optional SC on UV2, then it can be skipped (deleted);

ddd) if there is a repeating SE on UV2, then a copy of the repeating SE can be generated for it, which is inserted after the current one.

eee) since HC2 generally consists of several cells, the selection of the required cells can be made;

eeel) if the selected cell turns out to be degenerate, the choice is made one HC below and until the cell containing the EL is selected;

ee2) after selecting a cell containing EL, all degenerate cells, except for degenerate cells of HC2, are deleted, and the selected cell will replace the SC in which it is located, and thus goes one HC higher;

) if on UV2 there is a cell containing EL that can be selected, a return is made to step ccc); if not, then a transition is made to step ggg);

ggg) if there is an NTE on UV1, which is the name of the BNF, then go to step aaa), if not, then the SQL command generation cycle ends.

Thus, this method of generating syntactically and semantically correct commands can be applied to any final BNF, because the choice of EL leads to the transfer of a cell containing EL to the HC above. Further, for the purpose of more fully disclosing the present invention, it is necessary to consider semantic rules. Semantic rules (SP) are fragments of the text of the DBMS documentation, which impose additional restrictions on the execution (execution) of commands in the DBMS. The main feature of the RBNF is that it contains records of all SE, TE, STE, separators and repeatability characteristics, which are presented in the DBMS documentation. This allows you to use them when creating a CSP.

For example, for the create table / column definition command in the Oracle DBMS documentation, there is an indication:

"If you specify AS subquery when creating an index-organized table, then you must specify column, and you must omit data type."

In this specific example, which does not limit the scope of protection, the text fragment of the Oracle DBMS documentation is marked with quotation marks, which defines additional conditions that must be met for the create table / colimm definition command to work correctly, which is the Oracle DBMS control command. Such semantic rules in themselves cannot be recognized by the DBMS and must be formalized and presented in the form of a CSP. The main SP assigned to the team to be converted to a syntactically and semantically correct command can be formalized and represented as a set of pSP. The first column contains the number of the RPN element, the second column is the number of the RBNF element, the fourth column is the name of the RPN, the same as the RBNF to which the RPN is applied, the fifth column is the corresponding TE or NTE to which the rule applies, sixth column - possible operations on an element, due to which an element can be selected to which an element of CPD is applied, while the element can be checked for the value assigned to the element displayed in the seventh column, the eighth column is a logical nktsiya ninth column - comment tenth column - fragment documentation (in this particular example is not used), the eleventh column is an indication of the command to which the rule applies, the twelfth column is the rule status, the thirteenth column is a sign of rule activity. In addition, each CPN has a unique key with which the corresponding RBNF can be associated. As mentioned above, a unique rSP key is any unique key that can be generated from one or more records contained in a rSP associated with the corresponding rBNF. In particular, such a key can be a key generated from the line number (GO) in rBNF, the name rBNF (text BNF), and the record in one of the rSP cells. For example, for a CSP, a unique key may be a combination of entries from the NO, FILE NAME, and LINE columns located on the same row. Thus, when executing the procedure for generating syntactically and semantically correct instructions, the execution of each rule contained in the CPN is checked. For example, for the create table command, the pSP is checked: physical_properties, table_properties, table_properties. subquery, column definition. column, colurmi definition. datatype. If all CPDs are fulfilled, then the corresponding main SP is completed. In addition, in addition to the RPNs contained in the assigned main SP, other RPVs contained in other non-mainstream SPs can be applied to the command to be converted to a syntactically and semantically correct command.

In general terms, the formation of the CSP can be represented in the form of stages in which:

aaaa) a joint venture is selected from the DBMS documentation;

bbbb) a list of CSPs is formed to implement the selected joint venture;

SSSS) each CPN is a meta-description of the operations that are performed with the corresponding RBNF element.

The operations performed with the corresponding RBNF element may include, but are not limited to, a value verification operation, a value type verification operation, an element selection verification operation, an operation assigning a value to an element. Operations of logical union by functions OR or AND and operations of logical negation by NOT are applicable. There is a correspondence between rBNF and rSP, which is determined on the basis of the association of unique rBNF and rSP keys. During the generation of a syntactically and semantically correct command, the RBNF and the RSP are connected, the result of which is the creation of the resulting dynamic structure (RDS). RDS can be obtained using the operation of joining tables representing rBNF and RSP. Such an operation is a common operation on tables and, accordingly, is not further described. In this RDS, the first column corresponds to the number of entries in the RBNF, the second to the name of the RBNF (text BNF), the third to the entries in one of the RBNF cells, the fourth to the sign of the display of the element, the fifth to the sign of the choice of the element, the sixth to the sign of omission (deletion) of the element the seventh - to the type of operation on the element, the eighth - to the value specified for the element, the ninth - to the logical function for the operation, the tenth - to the value assigned to the element. When connecting rBNF and rSP, the correspondence of the unique keys rBNF and rSP is checked, due to which the correct SPs are assigned to the elements of rBNF. When the procedure for generating syntactically and semantically correct instructions is carried out, from the set of RDS, elements of the PSD corresponding to the commands to be converted into syntactically and semantically correct instructions are selected. After that, the execution of the pSP elements is checked and an SQL command is generated.

In FIG. 1 shows an exemplary embodiment of a method for generating syntactically and semantically correct instructions. As an example, but not limitation, a method 100 for generating a syntactically and semantically correct command by processing the original CREATE TABLE command, which is an Oracle DBMS control command, is described. At the software stage, the conversion of at least one a Backus-Naura text form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, into at least one Backus-Naura relational form containing a meta recognized by the database management system (DBMS) - A description of the command to be converted to a syntactically and semantically correct command. At step 120, the conversion of at least one text-based semantic rule containing at least one restriction on the execution of a command to be converted into a syntactically and semantically correct command into at least one relational semantic rule containing at least one DBMS recognized restriction on the execution of a command to be converted into a syntactically and semantically correct command. After that, at step 130, at least one command to be converted to a syntactically correct command is identified. Then, at step 140, at least a basic semantic rule is assigned to the instruction identified in step 130 and is to be converted into a syntactically correct command, the basic semantic rule including at least one CPN. At step 150, an RDS is generated for the identified instruction to be converted to a syntactically correct instruction. Then, at step 160, the elements of the basic semantic rule assigned at step 140 for the identified instruction to be converted to the syntactically correct instruction contained in the RDS generated for the identified instruction to be converted to the syntactically correct instruction are identified. At step 170, all elements of all the CSPs contained in the at least one basic semantic rule contained in the resulting dynamic structure generated for the identified team to be converted to are applied. syntactically and semantically correct command, to the identified command to be converted into syntactically and semantically correct command. Finally, at step 180, a syntactically and semantically correct instruction is generated on the basis of all elements of all CPNs applied to the identified instruction to be converted into a syntactically and semantically correct instruction from the at least one basic semantic rule contained in the RDS generated for an identified command to be converted to a syntactically and semantically correct command. In this case, before the start of the software stage, the stage of generating a relational description of the command syntax to be converted into a syntactically and semantically correct command can be performed. As part of the execution of the step, in particular, the meta-description of the command syntax is identified; identification of elements of the meta description of command syntax; assigning to each of the mentioned elements a unique identifier (GO), the ID being assigned in the order of the location of the said elements in the meta-description of the command syntax; forming a table containing all of the mentioned elements, each of the mentioned elements is contained in one column of the table on different rows of the table; identification of opening structural elements and closing structural elements among the mentioned elements contained in the table; generating bidirectional links between the corresponding opening structural elements and the closing structural elements; generating unidirectional hierarchical relationships between the said opening elements and the corresponding opening element located at the previous nesting level, moreover, the generation of unidirectional hierarchical relations is carried out for each opening element located at any of the nesting levels, except for the first nesting level. Additionally on this a stage can also be carried out the stage at which the generation of unidirectional lists of sets of meta-description elements of the command syntax metadata is located at the same nesting level, while unidirectional lists of sets of meta-description elements of the command syntax are limited to structural elements, while the sets of meta-description elements command syntax are located before or after the separator elements, and the generation of unidirectional lists of sets of elements of the meta description of the command syntax is carried out Appears for each level of nesting.

In FIG. 2, by way of example, but not limitation, an exemplary embodiment of the apparatus of the present invention is shown, namely, apparatus 200 for generating syntactically and semantically correct instructions, which may include, but is not limited to: a personal computer, a laptop computer, a tablet computer, a palmtop computer, smartphone, thin client and the like. The device is configured to access a data network and necessarily contains one or more processors 210, a computer-readable storage medium (memory) 220, input / output (I / O) modules 230 and input / output (I / O) ports 240. In memory 220, an example environment 250 is stored in which, using computer instructions or codes stored in the device memory 220, a procedure can be generated to generate syntactically and semantically correct instructions. Device memory 220 may be, but is not limited to: read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, CDROM, digital versatile disk (DVD) or other optical or holographic storage media; magnetic cassettes, magnetic tape, magnetic disk storage device or other magnetic storage devices, wave carriers or other storage medium that can be used to store the required information. The device is also contains one or more processors 210 that are designed to execute computer instructions or codes stored in the device memory in order to ensure that the procedure for generating syntactically and semantically correct instructions is executed. The computer commands executed by the device are commands that implement the steps described in this section of the application. In one of the embodiments of the present invention, the device 200 is an example, and not limitation, of the user's personal computer. This personal computer has an operating environment of 250, which as an example, and not limitation, is an operating system of the Windows or MacOS, or Unix family. In addition, the device comprises a memory made in one of the above embodiments, in which a computer application is stored, which is a corresponding set of computer instructions or codes that the user can manipulate. The procedure for generating a syntactically and semantically correct command is carried out through this application by selecting the command to be converted into a syntactically and semantically correct command. As an example, but not limitation, such a command can be an Oracle DBMS management command. In this exemplary embodiment of the invention, the user himself selects the command to be converted into a syntactically and semantically correct command, and then follows the prompts of the application by which the syntactically and semantically correct command is generated. The user also has the opportunity to create a template for generating a syntactically and semantically correct command (a generation script), or it can be automatically generated using a computer application or a block generating a script for generating a syntactically and semantically correct command according to the specified parameters. If device 200 is a thin client, in the aforementioned memory 220 does not store computer commands and program codes, and all the tasks are carried out on a server with which the device 200, which is presented as a thin client, is capable of communicating via a data network or other means of wired and wireless communication.

In FIG. 3 illustrates an exemplary embodiment of a system 300 for generating syntactically and semantically correct instructions, which comprises an apparatus 200 for generating syntactically and semantically correct instructions, a data network 310, one or more servers 320, and a database or database engine 330. Network 310 may include yourself, but not limited to, one or more local area networks (LAN) and / or wide area networks (WAN), or it can be an information and telecommunication network Internet, or an Intranet, or a virtual private network (VPN), etc. approved. System 300 includes said apparatus 200 for generating syntactically and semantically correct instructions. An apparatus 200 for generating syntactically and semantically correct instructions, as indicated above, is used to perform a procedure for generating syntactically and semantically correct instructions. In an exemplary embodiment, the apparatus 200 for generating syntactically and semantically correct instructions is the apparatus 200 for generating syntactically and semantically correct instructions, which has been described previously with reference to FIG. 2. Additionally, the system 300 includes a server 320, which may be: a personal computer, a laptop computer, a tablet computer, a PDA, a smartphone, a database machine, and the like. Server 320 provides data exchange control in system 300 and also provides data processing provided that one or more devices 200 for generating syntactically and semantically correct instructions are connected to it or when device 200 for generating syntactically and semantically correct instructions is a thin client, while all the computing power necessary to ensure the generation of syntactically and semantically correct instructions is located on server 320. Server 320 also has the ability to provide a virtual computing environment (Virtual Machine) to allow interaction between device 200 for generating syntactically and semantically correct commands and a database (database engine) 330 (DB). A database 330 may be, but is not limited to: a hierarchical database, a network database, a relational database, an object database, an object-oriented database, an object-relational database, a spatial database, a combination of these two or more databases, and the like. The database 330 stores data in memory, which can be accessed through the device 200 to generate syntactically and semantically correct instructions and the server 320. The memory may be, in particular, memory, as described previously. DB 330 is used for storing data, which is: instructions for the implementation of the procedure for generating syntactically and semantically correct instructions, DBMS documentation, text BNFs received by RBNFs, text SPs received by RSPs and other data necessary for the functioning of the system.

The present description of the invention demonstrates only a particular embodiment and does not limit other embodiments of the invention, since possible alternative embodiments of the invention, not beyond the scope of the information set forth in this application, should be obvious to a person skilled in the art having the usual qualification, which is calculated the claimed invention.

Claims

Claim

1. A method of generating syntactically and semantically correct commands, which consists in:

c) identifying at least one instruction to be converted to a syntactically and semantically correct instruction;

d) designating at least a basic semantic rule for an identified instruction to be converted into a syntactically and semantically correct instruction, the basic semantic rule including at least one relational semantic rule;

e) generating a resulting dynamic structure for the identified instruction to be converted to a syntactically and semantically correct instruction;

f) identifying the elements of said basic semantic rule for the identified instruction to be converted to syntactically and semantically correct command contained in the resulting dynamic structure generated for the identified command to be converted into syntactically and semantically correct command;

g) applying all the elements of all relational semantic rules contained in the said at least one basic semantic rule contained in the resulting dynamic structure formed for the identified team to be converted to a syntactically and semantically correct team to the identified team to be converted to syntactically and semantically correct command.

h) generating a syntactically and semantically correct command based on all elements of all relational semantic rules applied to the identified command to be converted into a syntactically and semantically correct command from the at least one basic semantic rule contained in the resulting dynamic structure generated for an identified command to be converted to a syntactically and semantically correct command.

2. The method according to p. 1, characterized in that they preliminarily form a relational description of the syntax of the command to be converted into a syntactically and semantically correct command.

3. The method according to p. 2, characterized in that the formation of a relational description of the syntax of the command to be converted into a syntactically and semantically correct command is carried out by performing the steps in which:

identify a meta description of command syntax;

identify the elements of the meta-description of the command syntax and assign each of the mentioned elements a unique identifier (ID), wherein W is assigned in order of location of said elements in the meta description of the command syntax;

form a table containing all of the mentioned elements, and each of these elements is contained in one column of the table on different rows of the table;

identifying opening structural elements and closing structural elements among said elements contained in the table, and generating bi-directional connections between respective opening structural elements and closing structural elements;

unidirectional hierarchical relations are generated between the said opening elements and the corresponding opening element located at the previous nesting level, and unidirectional hierarchical relations are generated for each opening element located at any of the nesting levels, except for the first nesting level.

4. The method according to p. 3, characterized in that the meta-description of the command syntax contains at least a combination of terminal elements, non-terminal elements and auxiliary elements.

5. The method according to p. 4, characterized in that the auxiliary elements are a combination of opening structural elements, closing structural elements and dividing elements.

6. The method according to p. 5, characterized in that the auxiliary elements additionally represent signs of repeatability.

7. The method according to p. 6, characterized in that at the stage of identification of the opening structural elements and closing structural elements are additionally identified signs of repeatability.

8. The method according to claim 7, characterized in that it further comprises the step of assigning an additional metadata element to the syntax of the command whose ID is close to W of the repeatability attribute a parameter that is different from the sign of repeatability, while the sign of repeatability is removed from the table.

9. The method according to p. 8, characterized in that it further comprises the step of generating unidirectional lists of sets of meta-description elements of the command syntax that are at the same nesting level, while unidirectional lists of sets of meta-description elements of the command syntax are limited to structural elements wherein the sets of meta-description elements of the command syntax are located before or after the separating elements, and the generation of unidirectional lists of sets of meta-description elements with command intaxis is implemented for each nesting level.

10. The method according to p. 9, characterized in that the Backus-Naur relational form, the basic semantic rule, the relational semantic rule, the resulting dynamic structure are tables containing at least records recorded in separate table cells having a row number and the column identifier, while the Backus-Naur relational form and the relational semantic rule have their own unique keys that can be associated with each other.

11. The method according to p. 10, characterized in that the relational form of Backus-Naur contains at least one of the structural elements, terminal elements, nonterminal elements, a sign of repeatability, or a combination thereof.

12. The method according to p. 11, characterized in that the structural elements are at least one of an opening bracket, a closing bracket, an opening curly bracket, a closing curly bracket, a vertical bar, or a combination thereof; terminal elements are at least keywords in bold upper case; nonterminal elements are at least keywords recorded in lower case the repeatability sign is at least an ellipsis, while the elements bounded by the opening bracket on the left and the closing bracket on the right are optional structural elements, the elements after which the repeatability sign is located are repeating elements, elements separated by a vertical bar are alternative elements.

13. The method according to p. 12 characterized in that when converting at least one text backus-Naur form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, at least at least one Backus-Naur relational form containing a recognized DBMS meta-description of a command to be converted to a syntactically and semantically correct command, optional structural elements can be deleted.

14. The method according to p. 12 characterized in that when converting at least one text backus-Naur form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, at least at least one Backus-Naur relational form containing a recognizable DBMS meta-description of a command to be converted to a syntactically and semantically correct command, repeated elements can be duplicated.

15. The method according to p. 12, characterized in that when converting at least one text backus-Naur form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, in at least one Backus-Naur relational form containing a recognizable DBMS meta-description of a command to be converted to a syntactically and semantically correct command, terminal elements and / or nonterminal elements can be selected for inclusion in the Backus-Naur relational form.

16. The method according to p. 15, characterized in that when converting at least one text backus-Naur form containing a meta-description of at least one command to be converted into a syntactically and semantically correct command, in at least one Backus-Naur relational form containing a recognizable DBMS meta-description of the command to be converted to a syntactically and semantically correct command, all alternative terminal elements and / or non-terminal elements can be selected for inclusion in the relational the new form of Backus-Naur.

17. The method according to any one of paragraphs. 1-16, characterized in that the relational Backus-Naur form has at least the attribute name of the relational Backus-Naur Form, the body attribute of the Backus-Naur form, the unique key attribute.

18. The method according to p. 17, characterized in that the unique key attribute is a combination of the number of the element of the Backus-Naur relational form, the name of the converted text backus-Naur form, and the entry in one of the cells of the mentioned backus-Naur relational form.

19. The method according to p. 18, characterized in that the row number of the Backus-Naur relational form, the name of the converted Backus-Naur text form and the entry in one of the cells of the mentioned Backus-Naur relational form are located in different columns on the same row of the table.

20. The method according to p. 19, characterized in that the basic semantic rule is a collection of relational semantic rules.

21. The method according to p. 20, characterized in that the relational semantic rule has at least the attribute name, attribute body, attribute unique key.

22. The method according to p. 21, characterized in that the table entries represent a combination of entries from at least the element number of the relational semantic rule, the unique identifier of the rule, the element number of the Backus-Naura relational form, the name of the relational semantic rule, the same as the name of the Backus-Naura relational form to which the relational semantic rule is applied, indications of a terminal element or non-terminal element to which the rule applies, indications of possible operations on said terminal element or non-terminal element, values, Assignment to said terminal element or nonterminal element, a logical function for operations on the said terminal element or a non-terminal element, comment, track documents, indications of a team, to be transformed into a syntactically and semantically correct command, rule status, tag rules activity.

23. The method according to p. 22, characterized in that the unique key attribute is a combination of the element number of the relational semantic rule, the name of the Backus-Naur relational form to which the relational semantic rule is applied, and entries in one of the cells of the mentioned relational semantic rule.

24. The method according to claim 23, wherein the line number of the relational semantic rule, the name of the Backus-Naur relational form to which the relational semantic rule is applied, and the entry in one of the cells of the said relational semantic rule are located in different columns on the same line of the said relational semantic rule.

25. The method according to any one of p. 1-16, 18-24, characterized in that the resulting dynamic structure is formed by the operation of connecting the relational form of Backus-Naur and the relational semantic rule, the elements of which are associated with elements of the relational form of Backus-Naur.

26. The method according to p. 25, characterized in that the resulting dynamic structure contains a combination of records from at least the element number in the Backus-Naur relational form, the name of the Backus-Naur relational form, the records in one of the cells of the Backus-Naur relational form, a flag for displaying an element, a flag for selecting an element, a flag for skipping an element at which the element is deleted, such as the operation on the element, the value specified for the element, the value assigned to the element, an indication of a logical function for the operation.

27. The method according to p. 26, characterized in that when generating the resulting dynamic structure, the coincidence of the unique keys of the relational form of the BNF and the relational semantic rule is checked, and if the unique keys coincide, the corresponding element of the relational semantic rule is applied to the corresponding element of the relational form of Backus-Naur .

28. The method according to any one of paragraphs. 1-16, 18-24, 26, 27, characterized in that the command to be converted to a syntactically and semantically correct command is an SQL command.

29. The method according to p. 28, characterized in that when identifying at least one team to be converted to a syntactically and semantically correct command, all relational semantic rules associated with the team to be converted to a syntactically and semantically correct team are identified, however, those relational semantic rules that refer to the said command can be distinguished from relational semantic rules that do not refer to the mentioned command.

30. The method according to p. 29, characterized in that when generating a syntactically and semantically correct command based on applied to the identified command to be converted into a syntactically and semantically correct command, all elements of all relational semantic rules, from the at least one basic semantic rule contained in the resulting dynamic structure generated for the identified mentioned command, the application of all elements of all relational semantic rules contained in the said at least one basic semantic rule is checked in the resulting dynamic structure formed for the identified team to be converted to syntactically and semantically correct A team at the same time providing a demonstration of all the elements mentioned mentioned all relational semantic rules with an indication of the performance of each of the elements of each of the relational semantic rules.

31. The method according to p. 30, characterized in that when generating a syntactically and semantically correct command based on all elements of all relational semantic rules from the at least one applied to the identified command to be converted to a syntactically and semantically correct command the basic semantic rule contained in the resulting dynamic structure generated for the identified mentioned team, the demonstration of the mentioned command is carried out, while such a demon the section contains all the terminal elements and non-terminal elements included in the command, and when a value is assigned to the non-terminal element, this value is shown, while the mentioned terminal elements and non-terminal elements can be applied to other commands to be converted to a syntactically and semantically correct command .

32. The method according to p. 31, characterized in that when identifying at least one command to be converted into a syntactically and semantically correct command, fragments of the DBMS documentation related to said command are shown.

33. The method according to any one of paragraphs. 1-16, 18-24, 26, 27, 29-32, characterized in that the action taken in relation to the identified command to be converted into a semantically and syntactically correct command can be canceled, while the procedure for generating syntactically and semantically correct command continues with the values and conditions corresponding to the values and conditions that were established before the cancellation of the said action.

34. A device for generating syntactically and semantically correct instructions, comprising:

one or more processors;

input / output modules (I / O);

I / O ports and

a memory containing program code, which upon execution causes the processor or processors of said device and / or device associated with said device to perform method steps according to any one of paragraphs. 1-33 formulas.

35. A system for generating syntactically and semantically correct instructions, comprising at least:

many devices for generating syntactically and semantically correct instructions executed in the form of devices according to claim 34 of the formula;

one or more servers providing regulation of data exchange in the system;

one database for storing data, configured to interact with the aforementioned devices for generating syntactically and semantically correct commands and one or more servers;

one data transmission network through which the interaction of the said devices generating syntactically and semantically correct commands, one or more servers and a database is carried out.

36. The system according to p. 35, characterized in that the generation of syntactically and semantically correct commands is carried out by one or more servers, and said devices for generating syntactically and semantically correct commands are a thin client.

37. The system of claim 36, wherein the database is used to store data representing at least one of a command for generating syntactically and semantically correct commands, DBMS documentation, Backus-Naur text forms, resulting relational forms Backus-Naura, textual semantic rules obtained by relational semantic rules.

38. The system of claim 37, wherein, when performing the procedure for generating syntactically and semantically correct instructions, said one or more servers request commands for performing the procedure for generating syntactically and semantically correct instructions before starting to generate syntactically and semantically correct instructions.

39. The system of claim 38, wherein said one or more servers regulate the exchange of data with said devices to perform a procedure for generating syntactically and semantically correct instructions through a virtual machine.

40. System according to any one of paragraphs. 35-39, characterized in that said data network is one of a local area network (LAN), wide area network (WAN), information and telecommunication network Internet, intranet, virtual private network (VPN).

41. The system of claim 40, wherein the organization of said database is one of the hierarchical organization of the database, network organization of the database, relational organization of the database, object organization of the database, object-oriented database organization, object-relational database organization, spatial database organization.

42. The system according to any one of p. 42, characterized in that the said database is a database machine.